[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-7032_versioncolours 
#6

See 
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7032_versioncolours/6/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Martin Kanters (Jira)]

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

Martin Kanters commented on MNG-5760:
-

[~max.ander...@jboss.com] thanks for your interest in this issue and I agree 
that the Hudson notifications are annoying, I'll see how/if we can avoid that.
Anyhow, it's a feature that will definitely be part of Maven 4. So keep your 
eye on that release :) 

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Max Rydahl Andersen (Jira)]

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

Max Rydahl Andersen commented on MNG-5760:
--

would love to keep following this issue but with hudson being massive noise 
generator I'll have to unsubscribe.

ping me if something need to test/verify/feedback on.

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build unstable in Jenkins: Maven » Maven TLP » maven-studies » maven-metrics #15

See 
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven-studies/job/maven-metrics/15/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build unstable in Jenkins: Maven » Maven TLP » maven » 
MNG-6012-Missing-Profile-At-End #15

See 
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-6012-Missing-Profile-At-End/15/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build unstable in Jenkins: Maven » Maven TLP » maven » REMOVE_DEPRECATED #15

See 
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/REMOVE_DEPRECATED/15/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build unstable in Jenkins: Maven » Maven TLP » maven » mng-5668-poc #15

See 
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/mng-5668-poc/15/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-5567 #15

See 
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-5567/15/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-6952 #15

See 
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-6952/15/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build unstable in Jenkins: Maven » Maven TLP » maven » MRESOLVER-94 #15

See 
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MRESOLVER-94/15/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build failed in Jenkins: Maven » Maven TLP » maven » MNG-6829 #15

See 
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-6829/15/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build unstable in Jenkins: Maven » Maven TLP » maven » Bananeweizen-MNG-6907 #16

See 
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/Bananeweizen-MNG-6907/16/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-6909 #15

See 
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-6909/15/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-6889 #15

See 
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-6889/15/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-6169/MNG-6556 #15

See 
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-6169%252FMNG-6556/15/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-6169/MNG-6553 #15

See 
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-6169%252FMNG-6553/15/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-6169/MNG-6555 #15

See 
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-6169%252FMNG-6555/15/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-6169/MNG-6550 #15

See 
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-6169%252FMNG-6550/15/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-6169/MNG-6552 #15

See 
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-6169%252FMNG-6552/15/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-6169/MNG-6554 #15

See 
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-6169%252FMNG-6554/15/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-6113 #3

See 
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-6113/3/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build unstable in Jenkins: Maven » Maven TLP » maven » MODELTESTS_IMPROVEMENT 
#16

See 
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MODELTESTS_IMPROVEMENT/16/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-6268 #2

See 
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-6268/2/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-4645+MNG-6772 #2

See 
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-4645+MNG-6772/2/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-4645 #6

See 
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-4645/6/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build unstable in Jenkins: Maven » Maven TLP » maven » checkstyle-next #3

See 
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/checkstyle-next/3/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build failed in Jenkins: Maven » Maven TLP » maven » MNG-7032_versioncolours #5

See 
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7032_versioncolours/5/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build unstable in Jenkins: Maven » Maven TLP » maven » system-line-separator #2

See 
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/system-line-separator/2/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build unstable in Jenkins: Maven » Maven TLP » maven » master #85

See 
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/master/85/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-7060 #5

See 
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7060/5/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-6169/MNG-6551 #14

See 
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-6169%252FMNG-6551/14/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 3.7.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build succeeded in Jenkins: Maven » Maven TLP » maven » MNG-6169/MNG-6556 #14

See 
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-6169%252FMNG-6556/14/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 3.7.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build succeeded in Jenkins: Maven » Maven TLP » maven » MNG-6169/MNG-6555 #14

See 
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-6169%252FMNG-6555/14/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 3.7.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build succeeded in Jenkins: Maven » Maven TLP » maven » MNG-6169/MNG-6553 #14

See 
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-6169%252FMNG-6553/14/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 3.7.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build failed in Jenkins: Maven TLP » maven » MNG-6169/MNG-6556 #46

See 
https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6556/46/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 3.7.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build failed in Jenkins: Maven TLP » maven » MNG-6512-build-11 #17

See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6512-build-11/17/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 3.7.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build failed in Jenkins: Maven TLP » maven » MNG-6909 #10

See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6909/10/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 3.7.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build failed in Jenkins: Maven TLP » maven » MNG-6169/MNG-6553 #40

See 
https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6553/40/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 3.7.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build failed in Jenkins: Maven TLP » maven » MNG-6169/MNG-6555 #47

See 
https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6555/47/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 3.7.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build failed in Jenkins: Maven TLP » maven » MNG-6169/MNG-6554 #39

See 
https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6554/39/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 3.7.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build failed in Jenkins: Maven TLP » maven » MNG-6952 #3

See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6952/3/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 3.7.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build failed in Jenkins: Maven TLP » maven » MPOM-215 #35

See https://builds.apache.org/job/maven-box/job/maven/job/MPOM-215/35/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 3.7.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build failed in Jenkins: Maven TLP » maven » REMOVE_DEPRECATED #18

See https://builds.apache.org/job/maven-box/job/maven/job/REMOVE_DEPRECATED/18/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 3.7.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build failed in Jenkins: Maven TLP » maven » testFor363 #3

See https://builds.apache.org/job/maven-box/job/maven/job/testFor363/3/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 3.7.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build failed in Jenkins: Maven TLP » maven » MNG-6169/MNG-6552 #40

See 
https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6552/40/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 3.7.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build failed in Jenkins: Maven TLP » maven » MNG-6169/MNG-6551 #46

See 
https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6551/46/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 3.7.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build failed in Jenkins: Maven TLP » maven » MNG-6829 #26

See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6829/26/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 3.7.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build failed in Jenkins: Maven TLP » maven » MNG-6169/MNG-6550 #43

See 
https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6550/43/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 3.7.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build failed in Jenkins: Maven TLP » maven » MNG-5567 #57

See https://builds.apache.org/job/maven-box/job/maven/job/MNG-5567/57/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 3.7.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build failed in Jenkins: Maven TLP » maven » slf4j-1.8-modules #36

See https://builds.apache.org/job/maven-box/job/maven/job/slf4j-1.8-modules/36/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 3.7.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build failed in Jenkins: Maven TLP » maven » MNG-6012-Missing-Profile-At-End #59

See 
https://builds.apache.org/job/maven-box/job/maven/job/MNG-6012-Missing-Profile-At-End/59/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 3.7.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build failed in Jenkins: Maven TLP » maven » mng-5668-poc #26

See https://builds.apache.org/job/maven-box/job/maven/job/mng-5668-poc/26/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 3.7.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build failed in Jenkins: Maven TLP » maven » MODELTESTS_IMPROVEMENT #28

See 
https://builds.apache.org/job/maven-box/job/maven/job/MODELTESTS_IMPROVEMENT/28/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 3.7.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build failed in Jenkins: Maven TLP » maven » Bananeweizen-MNG-6907 #5

See 
https://builds.apache.org/job/maven-box/job/maven/job/Bananeweizen-MNG-6907/5/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 3.7.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build failed in Jenkins: Maven TLP » maven » MRESOLVER-94 #5

See https://builds.apache.org/job/maven-box/job/maven/job/MRESOLVER-94/5/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 3.7.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build failed in Jenkins: Maven TLP » maven » MNG-6889 #5

See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6889/5/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 3.7.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build failed in Jenkins: Maven TLP » maven » MNG-6548 #24

See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6548/24/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 3.7.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build failed in Jenkins: Maven TLP » maven » MNG-6888 #5

See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6888/5/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 3.7.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Guy Brand (Jira)]

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

Guy Brand commented on MNG-5760:


[~mthmulders] This is now fixed with the other pull request you created. Thanks 
for fixing it that quickly!

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 3.7.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build unstable in Jenkins: Maven TLP » maven-studies » maven-metrics #22

See 
https://builds.apache.org/job/maven-box/job/maven-studies/job/maven-metrics/22/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 3.7.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build succeeded in Jenkins: Maven TLP » maven » master #446

See https://builds.apache.org/job/maven-box/job/maven/job/master/446/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 3.7.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build unstable in Jenkins: Maven TLP » maven-studies » maven-metrics #20

See 
https://builds.apache.org/job/maven-box/job/maven-studies/job/maven-metrics/20/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 3.7.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build failed in Jenkins: Maven TLP » maven » slf4j-1.8-modules #34

See https://builds.apache.org/job/maven-box/job/maven/job/slf4j-1.8-modules/34/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 3.7.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build failed in Jenkins: Maven TLP » maven » MPOM-215 #33

See https://builds.apache.org/job/maven-box/job/maven/job/MPOM-215/33/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 3.7.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build unstable in Jenkins: Maven TLP » maven » REMOVE_DEPRECATED #16

See https://builds.apache.org/job/maven-box/job/maven/job/REMOVE_DEPRECATED/16/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 3.7.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build unstable in Jenkins: Maven TLP » maven » mng-5668-poc #24

See https://builds.apache.org/job/maven-box/job/maven/job/mng-5668-poc/24/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 3.7.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build unstable in Jenkins: Maven TLP » maven » MNG-6012-Missing-Profile-At-End 
#57

See 
https://builds.apache.org/job/maven-box/job/maven/job/MNG-6012-Missing-Profile-At-End/57/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 3.7.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build unstable in Jenkins: Maven TLP » maven » MNG-6829 #24

See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6829/24/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 3.7.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build unstable in Jenkins: Maven TLP » maven » MNG-5567 #55

See https://builds.apache.org/job/maven-box/job/maven/job/MNG-5567/55/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 3.7.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build unstable in Jenkins: Maven TLP » maven » MNG-6889 #3

See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6889/3/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 3.7.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build unstable in Jenkins: Maven TLP » maven » MNG-6888 #3

See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6888/3/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 3.7.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build unstable in Jenkins: Maven TLP » maven » checkstyle-3.1 #2

See https://builds.apache.org/job/maven-box/job/maven/job/checkstyle-3.1/2/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 3.7.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build unstable in Jenkins: Maven TLP » maven » Bananeweizen-MNG-6907 #3

See 
https://builds.apache.org/job/maven-box/job/maven/job/Bananeweizen-MNG-6907/3/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 3.7.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build unstable in Jenkins: Maven TLP » maven » MNG-6169/MNG-6553 #38

See 
https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6553/38/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 3.7.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build unstable in Jenkins: Maven TLP » maven » MNG-6169/MNG-6556 #44

See 
https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6556/44/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 3.7.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build unstable in Jenkins: Maven TLP » maven » MODELTESTS_IMPROVEMENT #26

See 
https://builds.apache.org/job/maven-box/job/maven/job/MODELTESTS_IMPROVEMENT/26/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 3.7.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build unstable in Jenkins: Maven TLP » maven » MNG-6548 #22

See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6548/22/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 3.7.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build unstable in Jenkins: Maven TLP » maven » MNG-6169/MNG-6550 #41

See 
https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6550/41/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 3.7.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build unstable in Jenkins: Maven TLP » maven » MNG-6169/MNG-6551 #44

See 
https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6551/44/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 3.7.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build unstable in Jenkins: Maven TLP » maven » MNG-6169/MNG-6555 #45

See 
https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6555/45/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 3.7.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build unstable in Jenkins: Maven TLP » maven » MNG-6169/MNG-6554 #37

See 
https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6554/37/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 3.7.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build unstable in Jenkins: Maven TLP » maven » MRESOLVER-94 #3

See https://builds.apache.org/job/maven-box/job/maven/job/MRESOLVER-94/3/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 3.7.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build unstable in Jenkins: Maven TLP » maven » MNG-6169/MNG-6552 #38

See 
https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6552/38/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 3.7.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build unstable in Jenkins: Maven TLP » maven » MNG-6512-build-11 #15

See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6512-build-11/15/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 3.7.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build unstable in Jenkins: Maven TLP » maven » MNG-6909 #8

See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6909/8/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 3.7.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Guy Brand (Jira)]

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

Guy Brand commented on MNG-5760:


[~mthmulders] Great to hear! Thanks a lot!

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 3.7.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Maarten Mulders (Jira)]

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

Maarten Mulders commented on MNG-5760:
--

Good catch, [~Brand], thanks for bringing it up.

I have some other improvements for this feature as well, and I'll include the 
fix for this scenario. I'll also update the integration test to make sure it 
doesn't happen again.

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 3.7.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Guy Brand (Jira)]

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

Guy Brand commented on MNG-5760:


This change introduces a [possible 
{{NullPointerException}}|https://github.com/apache/maven/pull/342/files#diff-27608ebc026789b242c47348ac37dabfR65]
 as the {{project}} retrieved 
[here|https://github.com/apache/maven/pull/342/files#diff-27608ebc026789b242c47348ac37dabfR84]
 (coming from 
[{{LifecycleExecutionException#getProject()}}|https://github.com/apache/maven/blob/master/maven-core/src/main/java/org/apache/maven/lifecycle/LifecycleExecutionException.java#L74])
 can return {{null}}.

We face this error when executing our integration tests which execute {{mvn 
resources:resources}} without an existing project. With Maven {{3.6.3}} the 
following error is thrown: 
{code:java}
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time:  1.995 s
[INFO] Finished at: 2020-06-24T09:38:21+02:00
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-resources-plugin:3.1.0:resources (default-cli): 
Goal requires a project to execute but there is no POM in this directory 
(/foo). Please verify you invoked Maven from the correct directory. -> [Help 
1]{code}
Can this be fixed as part of that issue ? Shall I create another pull request 
or will you have a look at this [~mthmulders] ?

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 3.7.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build succeeded in Jenkins: Maven TLP » maven » master #434

See https://builds.apache.org/job/maven-box/job/maven/job/master/434/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 3.7.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build succeeded in Jenkins: Maven TLP » maven » MNG-6878 #8

See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6878/8/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 3.7.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)

[jira] [Commented] (MNG-5760) Add `-r/--resume` to automatically resume from the last failure point

[Hudson (Jira)]

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

Hudson commented on MNG-5760:
-

Build succeeded in Jenkins: Maven TLP » maven » master #430

See https://builds.apache.org/job/maven-box/job/maven/job/master/430/

> Add `-r/--resume` 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
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 3.7.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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  -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  -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
(v8.3.4#803005)