[ https://issues.apache.org/jira/browse/MNG-6012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16181248#comment-16181248 ]
Robert Scholte commented on MNG-6012: ------------------------------------- I've implemented MENFORCER-282, will be available with the next release. I've had a closer look at all the arguments you can pass to Maven. Profiles seems to be the only one not being verified. So maybe with a major release we should simple break the build, just like the rest. > 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: needing-scrub-3.4.0-fallout > > > 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.4.14#64029)