[
http://jira.codehaus.org/browse/MRM-872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=141344#action_141344
]
nicolas de loof commented on MRM-872:
-------------------------------------
"empty" here is not for "blank", but for XML root with no child element.
The issue depends on the repository ordering in the group. The "first win"
logic returns an empty metadata because the first repository didn't found the
artifact with its proxies and created an empty metadata file. This may be
considered to be a bug...
In any way, we MUST support metadatas merge for this use case :
A user has an issue with a maven plugin. As a nice guy, he creates an issue,
attach a patch, but to get quick fix he deploys a snapshot to its corporate
repo.
To get it using a group repository ("public" proxying public repos +
"corporate"), we need to merge the metadatas from both repositories, so that
the custom snapshot will get listed in metadatas + all available version on
public snapshot repositories.
> empty metadatas frmo a repository group
> ---------------------------------------
>
> Key: MRM-872
> URL: http://jira.codehaus.org/browse/MRM-872
> Project: Archiva
> Issue Type: Bug
> Affects Versions: 1.1
> Reporter: nicolas de loof
> Fix For: 1.1.1
>
>
> Here is my configuration :
> {noformat}
> group repository "maven"
> +-- managed repository "releases"
> +-- proxy connector to central
> +-- proxy connector to dev.java.net
> +-- proxy connector to jboss ...
> +-- managed repository "private"
> +-- proxy connector to corporate repository
> +-- proxy connector to second corporate repository
> {noformat}
> From a fresh new install, requesting "mvn eclipse:eclipse" fails with error :
> No versions are present in the repository for the artifact with a range
> [3.1.0,4.0.0)
> org.eclipse.core:resources:jar:null
> Browsing
> archvia/repository/maven/org/eclipse/core/resources/maven-metadata.xml
> returns a metadatafile with no entry.
> The metadata file in the "releases" repo (that merges all connectors
> metadatas) is correct with the expected versions available from central.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
