[
https://issues.apache.org/jira/browse/MNG-4917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17887244#comment-17887244
]
Alexander Kriegisch edited comment on MNG-4917 at 10/7/24 1:19 AM:
-------------------------------------------------------------------
[~gnodet], that the behaviour was there by design or even that it is documented
as-is does not mean that it makes much sense or is anything but
counter-intuitive and more harmful than helpful due to its raising false
expectations, stealing every developer's time playing with it and your time
answering related issues. The very fact that two workarounds - namely
{{<jdk>[1.)</jdk>}} and {{<condition>true</condition>}} - were suggested here
and that workarounds are even necessary for something so simple because the
existing option with a name implying to do what developers need, might clue you
in to the fact that something might be wrong in this picture.
The least you could do if you are so concerned about a some developers relying
on the existing behaviour, is to document the two workarounds in the two places
you pointed to earlier, explaining that if users want to _really_ activate a
profile by default, even if no other profile was activated manually or by a
condition, they could use those workarounds.
was (Author: kriegaex):
[~gnodet], that the behaviour was there by design or even that it is documented
as-is does not mean that it makes much sense or is anything but
counter-intuitive and more harmful than helpful due to its raising false
expectations, stealing every developer's time playing with it and your time
answering related issues. The very fact that two workarounds - namely
{{<jdk>[1.)</jdk>}} and {{<condition>true</condition>}} - were suggested here
and that workarounds are even necessary for something so simple because the
existing option with a name implying to do what developers need, might clue you
in to the fact that something might be wrong in this picture.
> 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: Guillaume Nodet
> 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.10#820010)
