[
https://issues.apache.org/jira/browse/MNG-4533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14948196#comment-14948196
]
Arend v. Reinersdorff commented on MNG-4533:
--------------------------------------------
Could this please be reopened? I would find this feature useful.
Another workaround I have seen to achieve an always active profile is to check
for existence of the pom.xml file:
{code}
<activation>
<file>
<exists>pom.xml</exists>
</file>
</activation>
{code}
> Add an always active profile activator
> --------------------------------------
>
> Key: MNG-4533
> URL: https://issues.apache.org/jira/browse/MNG-4533
> Project: Maven
> Issue Type: New Feature
> Components: Profiles
> Affects Versions: 2.2.1
> Reporter: Mark Hobson
> Priority: Minor
>
> There's currently no convenient method of always activating a profile, unless
> explicitly deactivated. There is of course {{activeByDefault}}, but this
> activator is deactivated if another profile within the same pom is activated.
> I propose something like:
> {noformat}
> <activation>
> <active/>
> </activation>
> {noformat}
> The current workaround is to activate on the absence of a property. For
> example:
> {noformat}
> <activation>
> <property>
> <name>!dummy</name>
> </property>
> </activation>
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
