[jira] [Commented] (IVY-1621) Create maven-metadata.xml in Maven repository (Nexus)

["Jaikiran Pai (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IVY-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17246494#comment-17246494 ] 

Jaikiran Pai commented on IVY-1621:
-----------------------------------

Failure of Ivy against Nexus 3 seems to be an major issue. I haven't had a chance to look into Nexus 3. I don't have a Nexus 3 (prod) installation handy to try out a few things. If there are some public facing Nexus 3 instances that I can check out and try this against, please do let me know. In the meantime, I will try and install Nexus 3 locally one of these days to give it a try.

> Create maven-metadata.xml in Maven repository (Nexus)
> -----------------------------------------------------
>
>                 Key: IVY-1621
>                 URL: https://issues.apache.org/jira/browse/IVY-1621
>             Project: Ivy
>          Issue Type: Improvement
>          Components: Maven Compatibility
>    Affects Versions: 2.5.0
>         Environment: * ivy 2.4.0 or 2.5.0
>  * Sonatype Nexus 3.x repo manager
>  * ant 1.10
>            Reporter: Alexander Ziller
>            Priority: Major
>
> h1. Goal:
> Use ivy dependency management where dependency has revision "latest.integration"
>  
> h1. Problems:
> Ivy cannot find the artifact with revision "latest.integration".
>  
> h1. 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!). {color:#de350b}This fails as IVY does not generate/upload the maven-metadata.xml file in the repository{color}
> *false*
> ivy attempts to do a HTML listing of the directory of the artifact. {color:#de350b}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{color}
>  
> h1. {color:#172b4d}possible Solution:{color}
>  
> {color:#172b4d}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.{color}
>  
> h1. {color:#172b4d}Further details:{color}
>  
> {color:#172b4d}another developer also found this problem and created an example code to verify the behavior:{color}
> {color:#172b4d}[https://github.com/dgeissl/nexus-ivy-example]{color}
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)