You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Paul Gier (JIRA)" <ji...@codehaus.org> on 2007/12/18 16:32:57 UTC
[jira] Created: (MNG-3326) Profile Deactivation
Profile Deactivation
--------------------
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
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>
--
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
[jira] Updated: (MNG-3326) Profile Deactivation Configuration
Posted by "Paul Gier (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Commented: (MNG-3326) Profile Deactivation Configuration
Posted by "Wim Deblauwe (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=183205#action_183205 ]
Wim Deblauwe commented on MNG-3326:
-----------------------------------
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).
> 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:
> <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>
--
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
[jira] Updated: (MNG-3326) Profile Deactivation Configuration
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MNG-3326:
------------------------------
Fix Version/s: (was: 3.x (to be reviewed))
3.1
> Profile Deactivation Configuration
> ----------------------------------
>
> Key: MNG-3326
> URL: http://jira.codehaus.org/browse/MNG-3326
> Project: Maven 2 & 3
> Issue Type: New Feature
> Components: Profiles
> Affects Versions: 2.0.8
> Reporter: Paul Gier
> Fix For: 3.1
>
>
> 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
[jira] Commented: (MNG-3326) Profile Deactivation Configuration
Posted by "Paul Benedict (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=207075#action_207075 ]
Paul Benedict commented on MNG-3326:
------------------------------------
I think this is a bit hacky.
> Profile Deactivation Configuration
> ----------------------------------
>
> Key: MNG-3326
> URL: http://jira.codehaus.org/browse/MNG-3326
> Project: Maven 2 & 3
> Issue Type: New Feature
> Components: Profiles
> Affects Versions: 2.0.8
> Reporter: Paul Gier
> Fix For: 3.1
>
>
> 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
[jira] Updated: (MNG-3326) Profile Deactivation
Posted by "Brian Fox (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Fox updated MNG-3326:
---------------------------
Fix Version/s: 2.1
> Profile Deactivation
> --------------------
>
> 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: 2.1
>
>
> 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>
--
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
[jira] Updated: (MNG-3326) Profile Deactivation Configuration
Posted by "Paul Gier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Gier updated MNG-3326:
---------------------------
Summary: Profile Deactivation Configuration (was: Profile Deactivation)
> 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: 2.1
>
>
> 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>
--
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