[IVYDE-236] Spring transitive dependencies resolved as latest.integration

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.1.0
• Fix Version/s: 2.1.0
• Component/s: classpath container
• Assignee: Nicolas Lalevée
• Reporter: AngerClown
• Created: 10/Feb/10 00:42
• Updated: 10/May/10 11:49
• Resolved: 10/May/10 11:49

Description

I am receiving resolution errors using IvyDE 2.1.0.201002011748-hudson-99 for Spring Framework related libraries. This may ultimately be an issue with Spring's ivy files, but the exact same setup is working with the 2.1.0.200911161501-hudson-79.log. Something appears to have changed with how resolution is being done between these two builds. In addition, running Ivy in Ant works so this is related to IvyDE and not base Ivy. Please see the attached for a testcase along with logs of the issue with both Hudson builds of IvyDE.

I am listing Spring Beans as a dependency in my project and it appears that Spring Core and it's dependencies are failing. Spring beans lists Spring Core as a dependency
<dependency org="org.springframework" name="org.springframework.core" rev="3.0.0.RELEASE" revConstraint="latest.integration" conf="compile->compile"/>.
IvyDE looks like it's trying to find the revConstraint of latest.integration for Core even though my project's ivy.xml specifies 3.0.0.RELEASE. IvyDE does download Spring Core but then ignores it and errors because it cannot find latest.integration.

Note that I have a <resolver> setup in ivysettings that uses the Spring Ivy repositories; I am not using the default ibiblio Maven repository. So, this issue appears with the Spring defined ivy.xml, not the ivy generated from M2 conversion.

Issue Links

• is related to: IVYDE-212 The workspace resolver doesn't resolve conflicts correctly