[
http://jira.codehaus.org/browse/MNG-3326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Gier updated MNG-3326:
---------------------------
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:
{code:xml}
<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>
{code}
was:
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>
> Profile Deactivation Configuration
> ----------------------------------
>
> Key: MNG-3326
> URL: http://jira.codehaus.org/browse/MNG-3326
> Project: Maven 2
> Issue Type: New Feature
> Components: Profiles
> Affects Versions: 2.0.8
> Reporter: Paul Gier
> Fix For: 3.x
>
>
> 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:
> {code:xml}
> <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>
> {code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
