[
https://issues.apache.org/jira/browse/IVY-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16796129#comment-16796129
]
Gianluca Sabato commented on IVY-1586:
--------------------------------------
Same here with Apache Jena jars. E.G.:
{code:xml}
<dependency>
<groupId>org.apache.jena</groupId>
<artifactId>jena-core</artifactId>
<classifier>tests</classifier>
<version>3.4.0</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>org.apache.jena</groupId>
<artifactId>jena-base</artifactId>
<classifier>tests</classifier>
<version>3.4.0</version>
<scope>test</scope>
</dependency>
{code}
I cannot share the code, but with an empty cache Ivy brings in the right jars
without "tests" classifier.
Second time running with a not empty cache, Ivy brings in the jars with the
"tests" classifier instead of the right ones.
Eclipse use them for compilation and deployment.
This is blocking bug for us, I hope it get addressed soon.
* Eclipse 4.10.0 64bit
* Apache IvyDE 2.2.0.final-201311091524-RELEASE
* Apache Ivy 2.5.0.cr1_20180412005306
> Retrieves test-library instead of binary-library
> ------------------------------------------------
>
> Key: IVY-1586
> URL: https://issues.apache.org/jira/browse/IVY-1586
> Project: Ivy
> Issue Type: Bug
> Components: Ant
> Affects Versions: 2.5.0-rc1
> Environment: Eclipse Photon 4.8.0 64bit
> Ant 1.10.3.v20180417-1627
> Apache IvyDE 2.2.0.final-201311091524-RELEASE
> Apache Ivy 2.5.0.cr1_20180412005306
> Reporter: Arni Schulze
> Priority: Blocker
> Attachments: Ant_1st_output.txt, Ant_2nd_output.txt, build.xml,
> ivy.xml
>
>
> If I delete the local Ivy cache and run my Ant script to retrieve
> "ch.quos.logback logback-classic 1.2.3" I get the correct library and its
> dependencies (see Ant_1st_output).
> But if I run the Ant script again (now having a local Ivy cache) it retrieves
> the test-library and the test-library of the dependencies instead of the
> correct ones (see Ant_2nd_output).
> I added minimalistic ivy.xml and Ant script. Because of the different
> behavior of the first and every other run, I think this is a bug in Ivy.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
