[
http://jira.codehaus.org/browse/MRM-463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joakim Erdfelt updated MRM-463:
-------------------------------
Description:
When dealing with metadata.xml files and proxying the merging of metadata is
not performed correctly.
Often ending up with a metadata.xml file with no versions specified.
Tasks
1) Re-enabled metadata tests in the archiva-proxy module.
2) Fix the proxy code (and possibly the tests) to ensure metadata.xml files are
merged correctly.
3) Create tests for 1 managed to multiple remote repos all with metadata.xml
for the same groupId:artifactId
4) Create tests for versionless and versioned metadata.xml files.
Note: Consider using the VersionComparator to obtain a unique list of sorted
(by version)
was:
When dealing with metadata.xml files and proxying the merging of metadata is
not performed correctly.
Often ending up with a metadata.xml file with no versions specified.
Tasks
HTML2TextReader.listItemPrefixRe-enabled metadata tests in the archiva-proxy
module.
HTML2TextReader.listItemPrefixFix the proxy code (and possibly the tests) to
ensure metadata.xml files are merged correctly.
HTML2TextReader.listItemPrefixCreate tests for 1 managed to multiple remote
repos all with metadata.xml for the same groupId:artifactId
HTML2TextReader.listItemPrefixCreate tests for versionless and versioned
metadata.xml files.
Note: Consider using the VersionComparator to obtain a unique list of sorted
(by
Fixing description that was mangled by mylyn plugin in eclipse (that apparently
doesn't like confluence/wiki-ness of a description.)
> Metadata merging doesn't work.
> ------------------------------
>
> Key: MRM-463
> URL: http://jira.codehaus.org/browse/MRM-463
> Project: Archiva
> Issue Type: Bug
> Components: remote proxy
> Affects Versions: 1.0-beta-2
> Reporter: Joakim Erdfelt
> Assignee: Joakim Erdfelt
> Priority: Blocker
> Fix For: 1.0-beta-3
>
>
> When dealing with metadata.xml files and proxying the merging of metadata is
> not performed correctly.
> Often ending up with a metadata.xml file with no versions specified.
> Tasks
> 1) Re-enabled metadata tests in the archiva-proxy module.
> 2) Fix the proxy code (and possibly the tests) to ensure metadata.xml files
> are merged correctly.
> 3) Create tests for 1 managed to multiple remote repos all with metadata.xml
> for the same groupId:artifactId
> 4) Create tests for versionless and versioned metadata.xml files.
> Note: Consider using the VersionComparator to obtain a unique list of sorted
> (by version)
--
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
