Attach files

Attach Screenshot

Add vote

Voters

Watch issue

Watchers

Create sub-task

Link

Clone

Update Comment Author

Replace String in Comment

Update Comment Visibility

Delete Comments

XML

Word

Printable

JSON

Details

Type: Improvement
Status: Open
Priority: Major
Resolution: Unresolved
Affects Version/s: 2.5.0
Fix Version/s: None
Component/s: Maven Compatibility
Labels:
None
Environment:
- ivy 2.4.0 or 2.5.0
- Sonatype Nexus 3.x repo manager
- ant 1.10

Description

Goal:

Use ivy dependency management where dependency has revision "latest.integration"

Problems:

Ivy cannot find the artifact with revision "latest.integration".

Cause:

Ivy uses 2 methods to find the revision "latest.integration" depending on setting "useMavenMetadata":

true

ivy attempts to load the file "maven-metadata.xml" which was supposed to be generated by the client uploading the artifact (in this case: ivy!). This fails as IVY does not generate/upload the maven-metadata.xml file in the repository

false

ivy attempts to do a HTML listing of the directory of the artifact. This fails because in Nexus3 the HTML browsing of the repo uses another base URL than it was done in Nexus2 or the Maven Repo

possible Solution:

During upload of an artifact (especially SNAPSHOT) let IVY generate and upload the maven-metadata.xml as well so it can use its own logic during download to find the correct version.