On Wed, Apr 28, 2010 at 04:03, Yossi Shaul <[email protected]> wrote: > Hi Bruno, > > When you request maven-metadata.xml from a virtual repository (e.g., > /repo), Artifactory merges the > maven-metadata.xml from all the repositories that belong to this virtual > repository. > It is possible that this maven metadata exists in more than one repository, > each one with different unique snapshots count. > To check how maven metadata looks on the specific real repository, either > go to it's parent folder in > the tree browser (br/com/company/jcompany_business/0.3.0-SNAPSHOT) and look > for it in the metadata tab or request > the file directly from the real repository. > > Is it the same one you get when requesting from /repo? > > Hi, Yossi.
Yes, I got the same wrong xml when download from real repo. I've just confirmed that doing a request on http://dev.company.com.br/maven2/libs-snapshots-local/br/com/company/jcompany_business/0.3.0-SNAPSHOT/maven-metadata.xml. There are 7 builds, but metadata puts the 5ยบ as the last. That is what was supposed to happen because this artifact exists only in one real repo. I think there's a bug on the class that generates that metadata, because import with ou without the old instance metadata, the new instance gives me a wrong metadata for almost all snapshots artifacts for this repo. What other version do you recommend me to test against this problem? 2.1.x? 2.2.2? Thanks -- BrunoJCM
------------------------------------------------------------------------------
_______________________________________________ Artifactory-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/artifactory-users
