[
https://issues.apache.org/jira/browse/MNG-5760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivange Larry Ndumbe updated MNG-5760:
-------------------------------------
Comment: was deleted
(was: Is this really a good idea. Say i have a five module project and during
the build there was an error in the third. Say in fixing the problem i decided
to make significant changes to previous modules that already built
successfully. Would this suggested behavior not brake my new build? I mean,
would it not ignore the changes i made to the other modules that had build
successfully and just continue building the module that failed?)
> All `-rf` to automatically resume from the last failure point
> -------------------------------------------------------------
>
> Key: MNG-5760
> URL: https://issues.apache.org/jira/browse/MNG-5760
> Project: Maven
> Issue Type: Improvement
> Components: Command Line
> Affects Versions: 3.2.5
> Reporter: Phillip Webb
> Priority: Trivial
>
> Currently when a multi-module build fails the {{mvn}} command line prints the
> following error:
> {noformat}
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR] mvn <goals> -rf :some-module-name
> {noformat}
> Since I almost always want to use this flag with the next build it would be
> very useful if you could type {{mvn <goals> -rf}} and have the project name
> inferred from the last failure rather than needing to copy/paste from the
> terminal.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)