On Tue, Mar 15, 2011 at 11:26 AM, Brett Cave <[email protected]> wrote:
>
>
> In 1 consumer project, I reference both the tar artifacts, and another
> references the jar
> dependencies {
> customConfig ("com.mycompany.package:some-model:$modelVersion@tar") {
> changing = true }
> }
> task extractTar(type: Copy) {
> into "somedir"
> configurations.customConfig.each {
> tarTree(it)
> }
> }
>
> and the other consumer (a different project in the same multi-project
> build):
> dependencies {
> compile ("com.mycompany.package:some-model:$modelVersion") { changing =
> true }
> }
>
I also noticed that the @tar dependency is listed differently to normal
dependencies in the resolved-.....consumer-client.xml file in cache:
<dependency org="com.mycompany.package" name="some-model"
rev="2.0.0-SNAPSHOT" changing="true" transitive="false"
conf="protodefs->default">
<artifact name="some-model" type="tar" ext="tar"
conf=""/>
</dependency>
whereas consumer-server resolves the jar as:
<dependency org="com.mycompany.package" name="some-model"
rev="2.0.0-SNAPSHOT" changing="true"
conf="compile->default;componentTest->default"/>
Could this be a bug in Ivy's dependency resolver?
