You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "Maria Odea Ching (JIRA)" <ji...@codehaus.org> on 2008/07/14 11:11:27 UTC

[jira] Issue Comment Edited: (MRM-872) empty metadatas frmo a repository group

    [ http://jira.codehaus.org/browse/MRM-872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=141695#action_141695 ] 

oching edited comment on MRM-872 at 7/14/08 4:11 AM:
---------------------------------------------------------------

Additional fixes in trunk -r676516:
1. generate checksums for the generated merged metadata
2. put the merged metadata & its checksums in the first repo where the metadata was found (with the filename: merged-maven-metadata.xml)
3. merge the metadata if and only if all the following conditions are met:
- the request was made to a repository group url
- the requested resource is a metadata file or a checksum file of a metadata
- the requested metadata file is at the project level, not version level
4. added test case when metadata checksums are requested after the metadata file (simulate Maven requests)

      was (Author: oching):
    Additional fixes in trunk -r676516:
1. generate checksums for the generated merged metadata
2. put the merged metadata & its checksums in the first repo where the metadata was found (with the filename: merged-maven-metadata.xml)
3. merge the metadata if and only if all the following conditions are met:
    - the request was made to a repository group url
    - the requested resource is a metadata file or a checksum file of a metadata
    - the requested metadata file is at the project level, not version level
4. added test case when metadata checksums are requested after the metadata file (simulate Maven requests)
  
> 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
>            Assignee: Maria Odea Ching
>             Fix For: 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