[
https://issues.apache.org/jira/browse/MNG-4917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17887333#comment-17887333
]
Guillaume Nodet commented on MNG-4917:
--------------------------------------
> > When we talk about a default value, this usually indicates "a value when no
> > other value was explicitly given".
> It's true. And the value is the activity, boolean. "The profile is active
> unless explicitly deactivated". Playing with other profiles should not affect
> this one.
I think in this case, it was meant as "part of the set of profiles active by
default", i.e. if no set of profiles if explicitely given.
> > what's the benefit of having an always active profile ?
> Say one have "sign" profile. Build artifacts should be signed by default, but
> there should be a way to disable signing to produce "weaker" build for debug
> purposes.
Makes total sense. Thx !
The current plan is to merged those two booleans somehow into the new
activation mechanism and to deprecate existing stuff, as part of MNG-8292.
Feel free to chime in if you want.
> 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
> Fix For: 4.1.0
>
> 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)
