You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (Jira)" <ji...@apache.org> on 2020/12/09 11:49:00 UTC

[jira] [Commented] (MNG-7051) Optionally skip non-existing profiles

    [ https://issues.apache.org/jira/browse/MNG-7051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17246472#comment-17246472 ] 

Michael Osipov commented on MNG-7051:
-------------------------------------

Please take the linked issues into consideration especially MNG-7011. We should disallow profile names with a hyphen at start to avoid ambiguity.

> Optionally skip non-existing profiles
> -------------------------------------
>
>                 Key: MNG-7051
>                 URL: https://issues.apache.org/jira/browse/MNG-7051
>             Project: Maven
>          Issue Type: Sub-task
>          Components: Profiles
>            Reporter: Maarten Mulders
>            Assignee: Maarten Mulders
>            Priority: Major
>
> For Maven 4, the behaviour of the {{-P}} command line option will change:
>  * {{-P apache-release}} will activate the *apache-release* profile. If such a profile cannot be found, the build will break.
>  * {{-P ?apache-release}} will activate the *apache-release* profile. If such a profile cannot be found, the build will continue but log a warning.
> {color:#ff0000}
> Note that this breaks the current behaviour of Maven 3 in two ways:
> {color}
> # {{-P apache-release}} will currently log a warning and not break the build. That behaviour can be restored by adding the {{?}}.
> # A profile that has an identifier that not valid (i.e., contains anything else than {{a}} - {{z}}, {{A}} to {{Z}}, {{0}} - {{9}}, {{-}}, {{_}} or {{.}}) will break the build.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)