Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Duplicate
-
2.1.0
-
None
-
None
-
Windows 7 64-bit, Eclipse Juno 4.2, Java 1.7.0_05 64-bit
Description
We've encountered resolution failures within Eclipse when the following conditions are met. Although we haven't tried all combinations, it seems to fit together based upon anecdotal evidence.
- The project publishing an artifact A exists in the Eclipse workspace.
- A second project B is also in the workspace and depends upon project A. The dependency includes the artifact sub-element within the dependency element.
- The rev isn't hard-coded.
Example fragment of ivy.xml:
<dependency org="com.myco" name="xyz" rev="latest.${release.type}"
transitive="false" conf="myco-shared, compile->default">
<artifact name="com.myco.xyz" type="jar"/>
</dependency>
We know the resolution works when any of these occur:
- The artifact sub-element is removed.
- The project dependee is closed/removed from workspace.
- rev is changed to a hard-coded value such as "latest.integration".
Based upon post: http://mail-archives.apache.org/mod_mbox/ant-ivy-user/201208.mbox/browser
Attachments
Issue Links
- duplicates
-
IVYDE-296 Dependencies (related projects) with artifact node can't resolve.
- Resolved