yes, that is a known issue and it was dicussed: [1] AFAIK the metadata is not really needed for downloading artifacts. The broken metadata derives from the fact that there is no practicable way (yet) to transfer our artifacts from the myfaces-staging dir to the apache rsync repo. There are theoretically three ways to transfer the artifacts. Each has a drawback:
1. Copy -->Corrupt metadata 2. Deploy them once more to the rsync repo -->distributed binaries are not those that the vote was for -->not allowed according to ASF standards 3. Use repositorytools:copy-repository (http://docs.codehaus.org/display/MAVENUSER/Repository+Tools) -->this tools is still in alpha state and Wendy advised against using it now --Manfred [1] http://www.nabble.com/how-to-transfer-artifacts-to-m2-ibiblio-rsync-repository-t3235673.html On 4/18/07, Paul Spencer <[EMAIL PROTECTED]> wrote:
maven-metadata.xml for the myfaces-shared-tomahawk artifact of the repository [1] looks incorrect. Specifically the list of versions is missing other version in the repository. All of the MyFaces shared artifacts have the same issue. Paul Spencer [1] http://repo1.maven.org/maven2/org/apache/myfaces/shared/myfaces-shared-tomahawk/maven-metadata.xml
-- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
