[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=17300959#comment-17300959
]
Maarten Mulders commented on MNG-6012:
--
{quote}[~mthmulders], I consider this resolved. WDYT?
{quote}
Yep, agreed, [~michael-o].
> 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)
[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=17300956#comment-17300956 ] Michael Osipov commented on MNG-6012: - [~mthmulders], I consider this resolved. WDYT? > 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)
[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=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)
[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=17232034#comment-17232034 ] Michael Osipov commented on MNG-6012: - * Option 1 is implemented by MNG-7019. * Option 2 shall break the build in the next major version of Maven if a non-existent profile is requested. > 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: 3.7.0-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)
[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=17231742#comment-17231742 ] Michael Osipov commented on MNG-6012: - [~khmarbaise], can we split this up in actually two tickets? Implementing the first point first? > 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: 3.7.0-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)
[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=16865954#comment-16865954 ] Michael Osipov commented on MNG-6012: - [~khmarbaise], do you want to pick this up for 3.6.2? > 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: 3.7.0-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 (v7.6.3#76005)
[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=16680269#comment-16680269 ] Hudson commented on MNG-6012: - Build failed in Jenkins: Maven TLP » maven » MNG-6012-Missing-Profile-At-End #16 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6012-Missing-Profile-At-End/16/ > 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: 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 (v7.6.3#76005)
[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=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)
[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=16179705#comment-16179705 ] Robert Scholte commented on MNG-6012: - No, my idea is an argumentless enforcer rule. It just verifies if the profile specified on the commandline exists in one the the projects. > 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)
[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=16179692#comment-16179692 ] Oliver Gierke commented on MNG-6012: That's a pity, as I then have to duplicate all profile names into that rule's configuration and it's easy to just forget to add to do so when a new one is added. > 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)
[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=16179671#comment-16179671 ] Robert Scholte commented on MNG-6012: - For now I'd suggest to resolve this with an enforcer rule, also much easier to release. > 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)
[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=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)
[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=15380727#comment-15380727
]
Robert Scholte commented on MNG-6012:
-
If you want a solution for this in 3.4.0 and we agree that we will fully
support {{--fail-level}} in the future, then we could implement this partially.
On the location where you do your check for missing profiles you verify if
{{--fail-level}} is {{warn}} and break the build in that case.
> 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.5.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)
[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=15380726#comment-15380726 ] Karl Heinz Marbaise commented on MNG-6012: -- I have to admit you are right...an 3.4.0-only option is not a good idea...so lets move it to 3.5.0... > 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.5.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)
[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=15380723#comment-15380723 ] Robert Scholte commented on MNG-6012: - I hope the conclusion will be that we're not going to solve this with this extra option. For that reason I'd prefer not to add this to 3.4.0 since it would be a 3.4.0-only option, which would be very weird. > 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)
[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=15380721#comment-15380721
]
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: 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)
[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=15380712#comment-15380712
]
Robert Scholte commented on MNG-6012:
-
A missing profile is a warning, so IMHO it is not worth an extra option. This
would open the door for any {{--fail-on-X}}. To me this should be fixed with an
enforcer rule instead.
> 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)
[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=15380708#comment-15380708 ] Karl Heinz Marbaise commented on MNG-6012: -- Current implementation available in https://git-wip-us.apache.org/repos/asf?p=maven.git;a=shortlog;h=refs/heads/MNG-6012-Missing-Profile-At-End > 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)
[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=15380694#comment-15380694 ] Karl Heinz Marbaise commented on MNG-6012: -- I've taken the liberty to add your comment to the newly created issue which is linked here cause that sounds like a general solution which is good. > 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)
[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=15380684#comment-15380684
]
Robert Scholte commented on MNG-6012:
-
I've been thinking the option {{--fail-level}} / {{-fl}} which is {{error}} by
default, but could be changed to {{warning}}/{{warn}}. We've had similar
request and they make sense: one should be able to execute a build without any
warnings.
I did an attempt to hook into the Logger to but that seems very tricky. The
other option is to have this level available in the API, so Maven core and
plugins can verify it for themselves and decide to throw an Exception. It is a
simple implementation, but now every component is responsible for checking it,
not really my preferred solution.
> 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)
[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=15380683#comment-15380683
]
Karl Heinz Marbaise commented on MNG-6012:
--
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)
[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=15380670#comment-15380670
]
Karl Heinz Marbaise commented on MNG-6012:
--
So I have taken a look into the code and #1 can simply being solved. But #2
would require a pom/settings.xml format change which I think can't happen in
Maven 3.X (Maven 4.?).
What do you think about an command line option like
{{--fail-on-missing-profiles}} ? Or should it be combined with
{{--fail-at-end}}, {{--fail-fast} or {{--fail-never}} ?
> 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)
