[
https://issues.apache.org/jira/browse/MNG-6268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17240207#comment-17240207
]
Michael Osipov commented on MNG-6268:
-------------------------------------
I think that just {{-r}} with all necessary information in
{{resume.properties}} will not work because it will introduce a chicken-and-egg
problem for {{-f}}. To read the properties you'd need to supply the path to
project to pick up properties, but the properties contain {{-f}}. Never ending
story. So we should not assume anything about {{-f}} in the properties.
So what to do now? We either say that {{-f}} is an achor for all other actions
Maven performs and this needs to be printed at any time OR we say all args are
equal and need to be all or nothing when one can resume. Even if we report
{{-f}} the rest will still be missing and needs to be obtained from shell
history and this will contain {{-f}} anyway.
I tend to say all or nothing while {{-f}} is being special. Having that said, I
am inclined to close this ticket as wontfix.
> When a reactor build fails Maven should include -f (if used) in command line
> suggestion
> ---------------------------------------------------------------------------------------
>
> Key: MNG-6268
> URL: https://issues.apache.org/jira/browse/MNG-6268
> Project: Maven
> Issue Type: Improvement
> Affects Versions: 3.5.0
> Reporter: Andreas Sewe
> Assignee: Michael Osipov
> Priority: Trivial
> Fix For: 4.0.x-candidate
>
>
> When a reactor build fails, Maven prints out a helpful suggestion on how to
> resume.
> {noformat}
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR] mvn <goals> -rf :example
> {noformat}
> Unfortunately, when running {{mvn}} with {{-f}}, this suggestion is wrong;
> Maven will either pick the wrong {{pom.xml}} or simply won’t find any; in
> either case, the {{pom.xml}} specified with {{-f}} is *crucial* information
> that was left out of the suggestion.
> FYI, this is related to MNG-6028, but covers a different bit of info that
> IMHO should be part of the suggestion. Hence this separate issue.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
