Details
Description
Profile definitions should have a way to add deactivation configuration similar to the activation configuration. So you could have a profile definition similar to this:
<profile> <id>my-profile</id> <activation> <property> <name>all.profiles.on</name> </property> </activation> <deactivation> <property> <name>all.profiles.off</name> </property> <jdk>1.6</jdk> </deactivation> </profile>
Issue Links
- is related to
-
MNG-2557
Various enhancements to profiles
-
We could use this too. I want to activate a certain profile (defined in my pom.xml) when releasing and de-active another profile (defined in my settings.xml) at the same time. The current workaround is to remove the <activeProfile/> line in my setttings.xml, but this easily forgotten (leading to a bad build in our case).