maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl Heinz Marbaise (JIRA)" <>
Subject [jira] [Commented] (MNG-6012) Missing profile is only notified at the end of a run
Date Sat, 16 Jul 2016 12:19:20 GMT


Karl Heinz Marbaise commented on MNG-6012:

Hm...thought also about enforcer but missing in general would mean to read the whole pom file
and activation/deactivation things of profiles needed to be done in enforcer also ? In core
it's relative easy to handle that...your argument about {{\-\-fail-on-X}} is valid sure...but
it is a convenience to fail if a profile can't be found at all which I have been faced myself
several time (in particular annoying for a long running build)...I would like to put that
into 3.4.0 and related to created issue based on your comments we should think about a better
solution in next releases....

> Missing profile is only notified at the end of a run
> ----------------------------------------------------
>                 Key: MNG-6012
>                 URL:
>             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

View raw message