腐败的常春藤XML缺少依赖项

时间:2015-06-12 22:05:27

标签: dependencies sbt ivy nexus

遇到重复出现的问题 - 使用以下堆栈: 关系 常春藤 SBT

库spray-can_2.11偶尔会在ivy-1.3.2.xml文件中缺少其依赖信息。结果是一个成功的构建和依赖树,但运行时NoClassDefFound异常。以下是腐败的一个例子:

ButtonBase

以下是擦除缓存后的文件&再次下载:

<?xml version="1.0" encoding="UTF-8"?>
<ivy-module version="2.0" xmlns:m="http://ant.apache.org/ivy/maven">
    <info organisation="io.spray"
        module="spray-can_2.11"
        revision="1.3.2"
        status="release"
        publication="20141008085147"
    >
        <license name="Apache 2" url="http://www.apache.org/licenses/LICENSE-2.0.txt" />
        <description homepage="http://spray.io">
        A suite of lightweight Scala libraries for building and consuming RESTful web services on top of Akka
        </description>
    </info>
    <configurations>
        <conf name="default" visibility="public" description="runtime dependencies and master artifact can be used with this conf" extends="runtime,master"/>
        <conf name="master" visibility="public" description="contains only the artifact published by this module itself, with no transitive dependencies"/>
        <conf name="compile" visibility="public" description="this is the default scope, used if none is specified. Compile dependencies are available in all classpaths."/>
        <conf name="provided" visibility="public" description="this is much like compile, but indicates you expect the JDK or a container to provide it. It is only available on the compilation classpath, and is not transitive."/>
        <conf name="runtime" visibility="public" description="this scope indicates that the dependency is not required for compilation, but is for execution. It is in the runtime and test classpaths, but not the compile classpath." extends="compile"/>
        <conf name="test" visibility="private" description="this scope indicates that the dependency is not required for normal use of the application, and is only available for the test compilation and execution phases." extends="runtime"/>
        <conf name="system" visibility="public" description="this scope is similar to provided except that you have to provide the JAR which contains it explicitly. The artifact is always available and is not looked up in a repository."/>
        <conf name="sources" visibility="public" description="this configuration contains the source artifact of this module, if any."/>
        <conf name="javadoc" visibility="public" description="this configuration contains the javadoc artifact of this module, if any."/>
        <conf name="optional" visibility="public" description="contains all optional dependencies"/>
    </configurations>
    <publications>
        <artifact name="spray-can_2.11" type="bundle" ext="jar" conf="master"/>
        <artifact name="spray-can_2.11" type="source" ext="jar" conf="sources" m:classifier="sources"/>
        <artifact name="spray-can_2.11" type="javadoc" ext="jar" conf="javadoc" m:classifier="javadoc"/>
    </publications>
    <dependencies>
    </dependencies>
</ivy-module>

有没有人观察到这个问题并且能够找出原因?

0 个答案:

没有答案