[jira] [Comment Edited] (MNG-6012) Missing profile is only notified at the end of a run

["Karl Heinz Marbaise (JIRA)" <ji...@apache.org>]

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

Karl Heinz Marbaise edited comment on MNG-6012 at 7/16/16 10:20 AM:
--------------------------------------------------------------------

So I have taken a look into the code and #1 can simply being solved. But #2 would require a pom/settings.xml format change which I think can't happen in Maven 3.X (Maven 4.?).
What do you think about an command line option like {{--fail-on-missing-profiles}} ? Or should it be combined with {{--fail-at-end}}, {{--fail-fast}} or {{--fail-never}} ?


was (Author: khmarbaise):
So I have taken a look into the code and #1 can simply being solved. But #2 would require a pom/settings.xml format change which I think can't happen in Maven 3.X (Maven 4.?).
What do you think about an command line option like {{--fail-on-missing-profiles}} ? Or should it be combined with {{--fail-at-end}}, {{--fail-fast} or {{--fail-never}} ?

> Missing profile is only notified at the end of a run
> ----------------------------------------------------
>
>                 Key: MNG-6012
>                 URL: https://issues.apache.org/jira/browse/MNG-6012
>             Project: Maven
>          Issue Type: New Feature
>    Affects Versions: 3.3.9
>            Reporter: Sebb
>             Fix For: 3.4.0
>
>
> A missing profile is only notified at the end of a run.
> Since this may mean that the run is useless, it would be helpful if:
> 1) It was also noted near the start, so the user could cancel the run.
> It's still helpful at the end, as it saves scrolling back to see if there was a problem.
> 2) There were an option to fail a run if a profile is not found. This option should be settable in a POM and in settings.xml



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)