[IVY-1580] Generated ivy.xml from pom with multiple dependencies with different classifier does not contain the main dependency

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.5.0-rc1
• Fix Version/s: 2.5.0
• Component/s: Maven Compatibility
• Assignee: Jaikiran Pai
• Reporter: Antoine Précigout
• Created: 23/May/18 07:54
• Updated: 23/Sep/19 17:48
• Resolved: 07/Sep/19 13:44

Description

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 :

<dependency>
  <groupId>org.slf4j</groupId>
  <artifactId>slf4j-log4j12</artifactId>
  <version>1.7.25</version>
</dependency>

Pom.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>

Generated Ivy.xml (dependency part) - 2.4.0

<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>

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

<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>

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

Issue Links

• duplicates: IVY-1586 Retrieves test-library instead of binary-library
• is duplicated by: IVYDE-387 Dependency jars removed from classpath after settings reloaded
• is duplicated by: IVY-1587 Wrong POM translation for dependencies appearing more than once
• relates to: IVY-1444 maven tests artifacts cannot be downloaded because they are mapped to private configurations
• relates to: IVY-1598 Ivy CLI resolve pulls in test scope from Maven parent pom