[ https://issues.apache.org/jira/browse/IVY-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16526218#comment-16526218 ]
jaikiran pai commented on IVY-1580: ----------------------------------- Daniel, thank you for the details. This indeed is a bug and I have a reproducible test case in my local workspace which reproduces this. This issue will occur on all systems irrespective of the operating system. I'll update this JIRA once I have a solution ready. > Generated ivy.xml from pom with multiple dependencies with different > classifier does not contain the main dependency > -------------------------------------------------------------------------------------------------------------------- > > Key: IVY-1580 > URL: https://issues.apache.org/jira/browse/IVY-1580 > Project: Ivy > Issue Type: Bug > Components: Maven Compatibility > Affects Versions: 2.5.0-rc1 > Reporter: Antoine Précigout > Assignee: jaikiran pai > Priority: Major > Attachments: logback-classic-1.1.7-with-ivy-2.4.0.xml, > logback-classic-1.1.7-with-ivy-2.5.0-rc1.xml > > > Hi, > Sorry for the title, it's a bit difficult to summerize the problem... > So, since we updated our Eclipse environment to Ivy 2.5.0-rc1 (available via > IvyDE), we encountered problems when resolving dependencies on our projects. > Following a little investigation, it appear that the generated ivy.xml from > the pom.xml of some dependencies differs from the previous version. > I think the slf4j-log4j12 package is a good exemple to illustrate my point : > +Details :+ > {code:xml} > <dependency> > <groupId>org.slf4j</groupId> > <artifactId>slf4j-log4j12</artifactId> > <version>1.7.25</version> > </dependency> > {code} > Pom.xml : > {code:xml} > <?xml version="1.0" encoding="UTF-8"?> > <project xmlns="http://maven.apache.org/POM/4.0.0" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 > http://maven.apache.org/xsd/maven-4.0.0.xsd"> > <modelVersion>4.0.0</modelVersion> > <parent> > <groupId>org.slf4j</groupId> > <artifactId>slf4j-parent</artifactId> > <version>1.7.25</version> > </parent> > <artifactId>slf4j-log4j12</artifactId> > <packaging>jar</packaging> > <name>SLF4J LOG4J-12 Binding</name> > <description>SLF4J LOG4J-12 Binding</description> > <url>http://www.slf4j.org</url> > <dependencies> > <dependency> > <groupId>org.slf4j</groupId> > <artifactId>slf4j-api</artifactId> > </dependency> > <dependency> > <groupId>log4j</groupId> > <artifactId>log4j</artifactId> > </dependency> > <dependency> > <groupId>org.slf4j</groupId> > <artifactId>slf4j-api</artifactId> > <type>test-jar</type> > <version>${project.version}</version> > <scope>test</scope> > </dependency> > </dependencies> > </project> > {code} > Generated Ivy.xml (dependency part) - 2.4.0 > {code:xml} > <dependencies> > <dependency org="org.slf4j" name="slf4j-api" rev="1.7.25" force="true" > conf="compile->compile(*),master(*);runtime->runtime(*)"/> > <dependency org="org.slf4j" name="slf4j-api" rev="1.7.25" force="true" > conf="test->runtime(*),master(*)"> > <artifact name="slf4j-api" type="test-jar" ext="jar" conf="" > m:classifier="tests"/> > </dependency> > [...] > </dependencies> > {code} > Two differents dependency entries : > - one for classic "jar" > - one for the type "test-jar". > In another hand : > Generated Ivy.xml (dependency part) - 2.5.0-rc1 > {code:xml} > <dependencies> > <dependency org="org.slf4j" name="slf4j-api" rev="1.7.25" force="true" > conf="compile->compile(*),master(*);runtime->runtime(*);test->runtime(*),master(*)"> > <artifact name="slf4j-api" type="test-jar" ext="jar" conf="" > m:classifier="tests"/> > </dependency> > [...] > </dependencies> > {code} > Only one dependency with artifact test-jar. > As a result for some of our projects to only get the dependency test-jar... > I think this is a bug, but maybe i did'nt understand a subtlety. > PS : Is it link to the correction of IVY-1484 ? > Thanks for your time :) -- This message was sent by Atlassian JIRA (v7.6.3#76005)