Brett Porter wrote: > On 09/02/2007, at 6:44 AM, Edwin Punzalan wrote: > >>> AFAIK the reason the poms are excluded is because they're modified >>> by the >>> release process; if the check for local modifications is run after >>> the pom >>> is modified, it's impossible to do a release. So this could >>> probably be fixed. >> That's correct, the pom is modified by the release... but the phase >> which checks for local modifications is run a few phases before >> that. So its safe to remove it from the ignore list. > > I agree.
It's convenient. Normally we just drop any SNAPSHOT releases from the POM and start the release process. Since the POM will be committed as part of the preparation, it saves an extra step. Otherwise we're forced to commit the POM with a comment like "prepare the release" manually and the plugin will do the same some instants later automatically. [snip] - Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
