You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Oliver Gierke (JIRA)" <ji...@apache.org> on 2017/09/25 11:00:00 UTC
[jira] [Commented] (MNG-6012) Missing profile is only notified at
the end of a run
[ https://issues.apache.org/jira/browse/MNG-6012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16178845#comment-16178845 ]
Oliver Gierke commented on MNG-6012:
------------------------------------
That's been moved to 3.5 but 3.5 has been around for a while now. What are the current plans for this?
> 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)