https://issues.apache.org/bugzilla/show_bug.cgi?id=48527
--- Comment #2 from Curt Arnold <[email protected]> 2010-06-16 00:12:09 EDT --- It appears that maven-metadata.xml is generated by merging the current metadata at the deployment repository with the generated metadata for the new version being deployed. I have not found a way to explicitly specify in the pom.xml what the full version history should look like. The schema for pom.xml does not have anything that looks like it. log4j is deployed first to a staging repo for voting before release. Unfortunately, this has resulted in generating a minimal maven-metadata.xml since the staging repo started empty. As far as I can tell, the best way to approach this is the manually manipulate the staging repository's maven-metadata.xml prior to release generation to put all the back versions into the history. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
