On Jan 10, 2008 9:16 AM, nicolas de loof <[EMAIL PROTECTED]> wrote: > Hello, > > I'd like to introduce a new option in the release:perform mojo to set some > additional profiles to get enabled during release (MRELEASE-313).
A big non-binding +1 - it would be very useful (at least IMHO). > In my projects I use to put all tasks non required at developemnt time in > "release" profile (example : add buildnumber in jar MANIFEST, ...) so that > the developer build gets simplier and quicker. During release, I need to > enabe this profile. To ensure this is not omitted, I'd like the release > plugin to have a parameter for some release-time required profiles. The > performRelease=true option is not enough as this enables the maven super-POM > profile that I don't want to use (I don't need sources.jar neither javadocs) > > I have a working change on the plugin, based on a new : > /** > * Comma separated profiles to enable on deployment, in addition to > active profiles > * for project execution. > * > * @parameter > */ > private String releaseProfiles; > > Any objection to commit this and deploy a new 2.0-beta-8-SNAPSHOT ? > > Nico. > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
