You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Maarten Mulders (Jira)" <ji...@apache.org> on 2020/12/09 09:21: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=17246381#comment-17246381 ]
Maarten Mulders commented on MNG-6012:
--------------------------------------
Work for option 2 is tracked in the second subtask, MNG-7051.
> 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
> Priority: Major
> Fix For: 4.0.x-candidate, 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
(v8.3.4#803005)