[
https://issues.apache.org/jira/browse/MNG-6028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16864977#comment-16864977
]
Robert Scholte commented on MNG-6028:
-------------------------------------
To me this is a workaround for the real issue: {{mvn <goals> -rf :module-a}}
doesn't work as expected.
The problem is actually bigger a lot bigger, but ideally {{-rf}} should be
enough to continue with the process.
This would mean Maven keep track of the original call which is the simplest to
solve.
The real challenge is with dependencies on previous build modules. They are not
"attached" anymore, so Maven would try to get them from the local repository.
This is one of the main reasons why I'd started removing final names from
packaging plugins so we can rely on predictable artifact names and re-use them
in cases if {{-rf}}.
I prefer to spend time on a better implementation than an adjusted message with
a workaround.
> When a reactor build fails maven should include current goals in resume
> suggestion
> ----------------------------------------------------------------------------------
>
> Key: MNG-6028
> URL: https://issues.apache.org/jira/browse/MNG-6028
> Project: Maven
> Issue Type: Improvement
> Affects Versions: 3.3.9
> Reporter: Axel Fontaine
> Priority: Major
> Fix For: 3.6.x-candidate, wontfix-candidate
>
>
> Start multiproject build at root with mvn clean install
> if module-a fails you currently get
> {noformat}[ERROR] After correcting the problems, you can resume the build
> with the command
> [ERROR] mvn <goals> -rf :module-a{noformat}
> to be able to easily copy-paste this it would be much nicer if the goals were
> already filled in:
> {noformat}[ERROR] After correcting the problems, you can resume the build
> with the command
> [ERROR] mvn clean install -rf :module-a{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
