If you do mvn deploy from your workspace directly into the repo, it will add the current version into the existing maven-metadata.xml. But if you can just copy the ones from the staged repo, only 1.6.2 can be seen. I don't think it will impact the maven resolution of older versions but it might change the discovery.
Thanks, Raymond ________________________________________________________________ Raymond Feng [email protected] Apache Tuscany PMC member and committer: tuscany.apache.org Co-author of Tuscany SCA In Action book: www.tuscanyinaction.com Personal Web Site: www.enjoyjava.com ________________________________________________________________ On Apr 12, 2011, at 1:03 PM, Simon Nash wrote: > I copied the 1.6.2 maven staging artifacts to m2-ibiblio-rsync-repository > using the instructions in [1]. Specifically, I did the following: > > > Or, instead of using the Maven stage plugin just manually copy the > > artifacts there: > > > > cp -p -v -R sca/ > > /x1/www/people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/tuscany/sca > > This overwrote all the maven-metadata.xml files under the target sca/ > directory with new files of the form: > > <?xml version="1.0" encoding="UTF-8" ?> > <metadata> > <groupId>org.apache.tuscany.sca</groupId> > <artifactId>tuscany-assembly</artifactId> > <version>1.6.2</version> > <versioning> > <versions> > <version>1.6.2</version> > </versions> > <lastUpdated>20110406144922</lastUpdated> > </versioning> > </metadata> > > These files refer only to the 1.6.2 version, and don't mention all > the other Tuscany versions in m2-ibiblio-rsync-repository. > > Is this a problem? If so, how can I fix it? > > Simon > > [1] http://tuscany.apache.org/making-releases.html >
