[
https://issues.apache.org/jira/browse/MNG-4917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17790346#comment-17790346
]
Alexander Kriegisch edited comment on MNG-4917 at 11/28/23 3:01 AM:
--------------------------------------------------------------------
Like others have said before, this mode is basically useless, because
* it does not do at all what a user would expect,
* it is unpredictable.
Please, either fix it (much preferred) or remove it from Maven completely to
prevent further harm. I cannot imagine any meaningful use case for the current
"implementation" (double quotes, because I consider it buggy).
*Edit:* If anyone is interested in my current workaround:
{code:xml}
<activation>
<jdk>[1.)</jdk>
</activation>
{code}
was (Author: kriegaex):
Like others have said before, this mode is basically useless, because
* it does not do at all what a user would expect,
* it is unpredictable.
Please, either fix it (much preferred) or remove it from Maven completely to
prevent further harm. I cannot imagine any meaningful use case for the current
"implementation" (double quotes, because I consider it buggy).
**Edit:** If anyone is interested in my current workaround:
{code:xml}
<activation>
<jdk>[1.)</jdk>
</activation>
{code}
> 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
> 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)
