Barrie Treloar wrote: > Apologies for the noob question, but how do I test the stage release? > (I had a quick look at > http://docs.codehaus.org/display/MAVEN/Development+Process and > http://docs.codehaus.org/display/MAVEN/Development+Procedures but > couldn't find it). > > Is it just a matter of defining > http://people.apache.org/~brianf/staging-repository/ as a repo in > settings.xml as: > > <profile> > <id>staging</id> > <repositories> > <pluginRepositories> > <pluginRepository> > <id>staging</id> > <name>Maven Plugin Staging Repository</name> > <url>http://people.apache.org/~brianf/staging-repository/</url> > <releases> > <enabled>true</enabled> > </releases> > <snapshots> > <enabled>false</enabled> > </snapshots> > </pluginRepository> > </pluginRepositories> > </profile>
That would work fine to allow trialling the plugin against various projects on the command line. The other part of testing would be to check out the svn tag and verify that it builds. > What happens when the real thing is released? Will my local repo be > polluted with the staging details and I need to clean it up? If you don't build it yourself, and the staged version is released unchanged, then that's mostly not a problem - though there'd be some metadata xml files left over in the local repo. If you do build it yourself, then you'd *hope* you'd have an exact workalike to the release, but it won't be bytewise identical, so you probably ought to call that pollution, and clean it up. And of course, there's the possibility that this staging iteration doesn't succeed, in which case, it's *definitely* pollution in the local repo that needs to be cleaned up. Max.
signature.asc
Description: OpenPGP digital signature
