maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl Heinz Marbaise (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (MNG-6012) Missing profile is only notified at the end of a run
Date Sat, 16 Jul 2016 11:29:20 GMT

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

Karl Heinz Marbaise edited comment on MNG-6012 at 7/16/16 11:29 AM:
--------------------------------------------------------------------

So made an implementation which looks like this:
{code}
~/ws-git/javaee (master *)$ ~/tools/maven-test/apache-maven-3.4.0-SNAPSHOT/bin/mvn clean package
-Pfirst,second --fail-on-missing-profiles
[INFO] Scanning for projects...
[ERROR] The requested profile "second" could not be activated because it does not exist.
[ERROR] One or more profiles you have requested to be activated do not exist. -> [Help
1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following
articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException{code}
or if I omit {{\-\-fail-on-missing-profiles}} it will look like this:
{code}
~/ws-git/javaee (master *)$ ~/tools/maven-test/apache-maven-3.4.0-SNAPSHOT/bin/mvn clean package
-Pfirst,second
[INFO] Scanning for projects...
[WARNING] The requested profile "second" could not be activated because it does not exist.
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO]
[INFO] parent
[INFO] domain.
....
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] parent ............................................. SUCCESS [  1.585 s]
[INFO] domain ............................................. SUCCESS [ 13.949 s]
[INFO] service-client ..................................... SUCCESS [  0.085 s]
[INFO] webgui ............................................. SUCCESS [  0.505 s]
[INFO] service ............................................ SUCCESS [  0.360 s]
[INFO] app ................................................ SUCCESS [  0.270 s]
[INFO] appasm ............................................. SUCCESS [  0.211 s]
[INFO] shade .............................................. SUCCESS [  0.425 s]
[INFO] assembly ........................................... SUCCESS [  1.700 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 19.645 s
[INFO] Finished at: 2016-07-16T13:12:39+02:00
[INFO] Final Memory: 35M/701M
[INFO] ------------------------------------------------------------------------
[WARNING] The requested profile "second" could not be activated because it does not exist.
{code}



was (Author: khmarbaise):
So made an implementation which looks like this:
{code}
~/ws-git/javaee (master *)$ ~/tools/maven-test/apache-maven-3.4.0-SNAPSHOT/bin/mvn clean package
-Pfirst,second --fail-on-missing-profiles
[INFO] Scanning for projects...
[WARNING] The requested profile "second" could not be activated because it does not exist.
[ERROR] One or more profiles you have requested to be activated do not exist. -> [Help
1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following
articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
{code}
or if I omit {{\-\-fail-on-missing-profiles}} it will look like this:
{code}
~/ws-git/javaee (master *)$ ~/tools/maven-test/apache-maven-3.4.0-SNAPSHOT/bin/mvn clean package
-Pfirst,second
[INFO] Scanning for projects...
[WARNING] The requested profile "second" could not be activated because it does not exist.
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO]
[INFO] parent
[INFO] domain.
....
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] parent ............................................. SUCCESS [  1.585 s]
[INFO] domain ............................................. SUCCESS [ 13.949 s]
[INFO] service-client ..................................... SUCCESS [  0.085 s]
[INFO] webgui ............................................. SUCCESS [  0.505 s]
[INFO] service ............................................ SUCCESS [  0.360 s]
[INFO] app ................................................ SUCCESS [  0.270 s]
[INFO] appasm ............................................. SUCCESS [  0.211 s]
[INFO] shade .............................................. SUCCESS [  0.425 s]
[INFO] assembly ........................................... SUCCESS [  1.700 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 19.645 s
[INFO] Finished at: 2016-07-16T13:12:39+02:00
[INFO] Final Memory: 35M/701M
[INFO] ------------------------------------------------------------------------
[WARNING] The requested profile "second" could not be activated because it does not exist.
{code}


> 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)

Mime
View raw message