[
https://issues.apache.org/jira/browse/MNG-4917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17507172#comment-17507172
]
Delany commented on MNG-4917:
-----------------------------
When I need my _snapshot_ profile to be mutually exclusive to my _release_
profile, for example, I bind them both to the presence/absence of a property.
So there are ways of achieving this same effect, and without the side-effect of
prohibiting the use of more opt-in profiles.
That said, I don't like the idea of changing behaviour. Why not deprecate it in
3.9.0 and remove it in 4.0.0, while adding
<activation><active>true</active></activation>
or better still
<activation>true</activation>
> Profile not active even though it has activeByDefault set to true
> -----------------------------------------------------------------
>
> Key: MNG-4917
> URL: https://issues.apache.org/jira/browse/MNG-4917
> Project: Maven
> Issue Type: Bug
> Components: Profiles
> Affects Versions: 3.0, 3.8.5
> Reporter: Benson Margulies
> Assignee: Benjamin Bentmann
> Priority: Major
> Attachments: pom.xml
>
>
> I've got a parent pom with a profile with
> <activeByDefault>true</activeByDefault>.
> You can retrieve it for yourself via git clone
> git://git.apache.org/webservices-xmlschema.git.
> The problem is the sourcecheck profile in the parent pom.
> running mvn -Psourcecheck works as expected, but running without the -P fails
> to activate the profile.
> the help plugin, I think, has separate problems in this area, or perhaps it's
> not supposed to look at -P?
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
