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

Hudson commented on MNG-7051:
-----------------------------

Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-6889 #16

See 
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-6889/16/

> 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: Martin Kanters
>            Priority: Major
>             Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> 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)

Reply via email to