[
https://jira.codehaus.org/browse/MNG-2557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly updated MNG-2557:
----------------------------------
Fix Version/s: (was: 3.2)
Issues to be reviewed for 4.x
> Various enhancements to profiles
> --------------------------------
>
> Key: MNG-2557
> URL: https://jira.codehaus.org/browse/MNG-2557
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Profiles
> Affects Versions: 2.0.4
> Reporter: Jimisola Laursen
> Fix For: Issues to be reviewed for 4.x
>
>
> The current support for profiles is somewhat limited and this issue report
> proposes some enhancements to profiles for ease and flexibility of use.
> Enhancement #1: Make it possible to have profiles that mutually exclude each
> other. A profile should be able to exclude one or more other profiles.
> Example of usage: We have a couple of profiles for databas settings (MSSQL,
> PostgreSQL and Derby). Only one of these profiles should be able to be active
> at the same time. Today, we can't express this in the profiles section.
> Enhancement #2: Make it possible to deactivate profiles from the command line.
> Example of usage: User and/or project has a set of profiles that are activate
> per default. The user wants to temporary disable on or more of these (by
> temporary I mean for one execution).
> Possible syntax might be: mvn -PsomeProfile=inactive|false|no or perhaps a
> separate command line switch.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira