On 25 April 2012 11:18, Jörg Schaible <joerg.schai...@scalaris.com> wrote: > Hi Sebb, > > sebb wrote: > >> On 25 April 2012 07:48, Jörg Schaible <joerg.schai...@scalaris.com> wrote: > > [snip] > >>> - rc: the one we use >> >> That was the one we used for creating RCs prior to Nexus. >> >>> - release: automatically activated by M2 (IIRC) >> >> This is the one I normally use. >> >> I think rc and release are fairly similar. > > Well, the profile "release" is activated by the plugin as default, see > (default) configuration of the release plugin. As long as no-one overwrites > the setting ... ;-)
I don't use the release plugin, because I don't like the way it messes with trunk. I prefer to create the tag from clean trunk checkout + version updates. Much safer that way. >> However, I'm not sure either can be used for releasing the parent POM. > > "release" (resp. the configured ones) should be active nevertheless, you may > add more using -P option. > >>> - apache-release: outdated? >> >> This is the one in the ASF pom; IIRC it clashes with our requirements. > > OK. > >>>> Are any >>>> of the commons projects currently multimodule builds? >>> >>> http://wiki.apache.org/commons/CreatingReleases > > We should finalize it. Gary, did you follow now that steps? > > And we must update or drop http://commons.apache.org/releases/index.html Yes. > Cheers, > Jörg > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
