[
https://issues.apache.org/jira/browse/MNG-4917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17887263#comment-17887263
]
Guillaume Nodet edited comment on MNG-4917 at 10/7/24 6:55 AM:
---------------------------------------------------------------
Actually, that would lead to yet another set of boolean options which are
mutually exclusive. So a better way may be to define
{code}
<activation>
<default> inactive | active | if-none-else </default>
</activation>
{code}
Anyway, one question that comes to my mind is: what's the benefit of having an
always active profile ? Why not injecting the content of the profile directly
in the project ?
was (Author: gnt):
Actually, that would lead to yet another set of boolean options which are
mutually exclusive. So a better way may be to define
{code}
<activation>
<default> inactive | active | if-no-else </active>
</activation>
{code}
Anyway, one question that comes to my mind is: what's the benefit of having an
always active profile ? Why not injecting the content of the profile directly
in the project ?
> 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)
