[jira] Commented: (MRM-463) Metadata merging doesn't work.

2007-08-25 Thread Joakim Erdfelt (JIRA)

[ 
http://jira.codehaus.org/browse/MRM-463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_105707
 ] 

Joakim Erdfelt commented on MRM-463:


Baseline components for metadata merging i feel are stable and have adequate 
unit tests.
See revision 569760.

The Proxy changes and new Consumers I'm still working on.
They will be committed within the next 24 to 48 hours.

 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-1
Reporter: Joakim Erdfelt
Assignee: Joakim Erdfelt
Priority: Blocker
 Fix For: 1.0-beta-2


 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




[jira] Commented: (MRM-463) Metadata merging doesn't work.

2007-08-20 Thread arno koehler (JIRA)

[ 
http://jira.codehaus.org/browse/MRM-463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_105210
 ] 

arno koehler commented on MRM-463:
--

I spoke to Joakim on the IRC channel #archiva - about Archiva not updating new 
released JAR versions from our repository, he told me it is related to this 
item; therefore it has my voting (please fix it).

 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-1
Reporter: Joakim Erdfelt
Assignee: Joakim Erdfelt
Priority: Blocker
 Fix For: 1.0-beta-2


 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




[jira] Commented: (MRM-463) Metadata merging doesn't work.

2007-08-14 Thread Joakim Erdfelt (JIRA)

[ 
http://jira.codehaus.org/browse/MRM-463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_104877
 ] 

Joakim Erdfelt commented on MRM-463:


Discussion on this jira has been started in archiva-dev mailing list.
See http://www.nabble.com/MRM-463---metadata-handling---merging-tf4270417.html

 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-1
Reporter: Joakim Erdfelt
Assignee: Joakim Erdfelt
Priority: Blocker
 Fix For: 1.0-beta-2


 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




[jira] Commented: (MRM-463) Metadata merging doesn't work.

2007-08-14 Thread Joakim Erdfelt (JIRA)

[ 
http://jira.codehaus.org/browse/MRM-463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_104880
 ] 

Joakim Erdfelt commented on MRM-463:


Even though this is assigned to me, please feel free to work on it, if you feel 
you can contribute. ;-)

 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-1
Reporter: Joakim Erdfelt
Assignee: Joakim Erdfelt
Priority: Blocker
 Fix For: 1.0-beta-2


 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