[
https://jira.codehaus.org/browse/MRELEASE-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte updated MRELEASE-876:
------------------------------------
Description:
When uploading a release fails because the repository manager (Nexus) looses
the network connection for whatever reason, it would be great to be able to
resume the release from the point where the upload failed. Maven specifically
instructs you to do so (but fails to remember the command line that was
provided to it)
When trying to continue the release perform using -rf :module in a git
environment with a local checkout, the release plugin conveniently forgets the
scm location or requires one where there is none...
{noformat}
$ mvn -ff release:perform -DlocalCheckout=true -Dtag=wicket-6.15.0
-Papache-release -rf :wicket-native-websocket-core
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO]
[INFO] Wicket Native WebSocket Core
[INFO] Wicket Native WebSocket Jetty
[INFO] Wicket Native WebSocket Jetty 9
[INFO] Wicket Native WebSocket Tomcat 7.x
[INFO] Wicket Common Tests
[INFO]
[INFO] Using the builder
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder
with a thread count of 1
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Wicket Native WebSocket Core 6.15.1-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-release-plugin:2.3.2:perform (default-cli) @
wicket-native-websocket-core ---
[ERROR] No SCM URL was provided to perform the release from
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Wicket Native WebSocket Core ...................... FAILURE [ 0.471 s]
[INFO] Wicket Native WebSocket Jetty ..................... SKIPPED
[INFO] Wicket Native WebSocket Jetty 9 ................... SKIPPED
[INFO] Wicket Native WebSocket Tomcat 7.x ................ SKIPPED
[INFO] Wicket Common Tests ............................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1.467 s
[INFO] Finished at: 2014-04-16T00:36:49+01:00
[INFO] Final Memory: 18M/81M
[INFO] ------------------------------------------------------------------------
{noformat}
was:
When uploading a release fails because the repository manager (Nexus) looses
the network connection for whatever reason, it would be great to be able to
resume the release from the point where the upload failed. Maven specifically
instructs you to do so (but fails to remember the command line that was
provided to it)
When trying to continue the release perform using -rf :module in a git
environment with a local checkout, the release plugin conveniently forgets the
scm location or requires one where there is none...
$ mvn -ff release:perform -DlocalCheckout=true -Dtag=wicket-6.15.0
-Papache-release -rf :wicket-native-websocket-core
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO]
[INFO] Wicket Native WebSocket Core
[INFO] Wicket Native WebSocket Jetty
[INFO] Wicket Native WebSocket Jetty 9
[INFO] Wicket Native WebSocket Tomcat 7.x
[INFO] Wicket Common Tests
[INFO]
[INFO] Using the builder
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder
with a thread count of 1
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Wicket Native WebSocket Core 6.15.1-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-release-plugin:2.3.2:perform (default-cli) @
wicket-native-websocket-core ---
[ERROR] No SCM URL was provided to perform the release from
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Wicket Native WebSocket Core ...................... FAILURE [ 0.471 s]
[INFO] Wicket Native WebSocket Jetty ..................... SKIPPED
[INFO] Wicket Native WebSocket Jetty 9 ................... SKIPPED
[INFO] Wicket Native WebSocket Tomcat 7.x ................ SKIPPED
[INFO] Wicket Common Tests ............................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1.467 s
[INFO] Finished at: 2014-04-16T00:36:49+01:00
[INFO] Final Memory: 18M/81M
[INFO] ------------------------------------------------------------------------
> Resume a release:perform in multimodule git project fails
> ---------------------------------------------------------
>
> Key: MRELEASE-876
> URL: https://jira.codehaus.org/browse/MRELEASE-876
> Project: Maven Release Plugin
> Issue Type: Bug
> Affects Versions: 2.3.2, 2.5
> Reporter: Martijn Dashorst
>
> When uploading a release fails because the repository manager (Nexus) looses
> the network connection for whatever reason, it would be great to be able to
> resume the release from the point where the upload failed. Maven specifically
> instructs you to do so (but fails to remember the command line that was
> provided to it)
> When trying to continue the release perform using -rf :module in a git
> environment with a local checkout, the release plugin conveniently forgets
> the scm location or requires one where there is none...
> {noformat}
> $ mvn -ff release:perform -DlocalCheckout=true -Dtag=wicket-6.15.0
> -Papache-release -rf :wicket-native-websocket-core
> [INFO] Scanning for projects...
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] Wicket Native WebSocket Core
> [INFO] Wicket Native WebSocket Jetty
> [INFO] Wicket Native WebSocket Jetty 9
> [INFO] Wicket Native WebSocket Tomcat 7.x
> [INFO] Wicket Common Tests
> [INFO]
> [INFO] Using the builder
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder
> with a thread count of 1
> [INFO]
>
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Building Wicket Native WebSocket Core 6.15.1-SNAPSHOT
> [INFO]
> ------------------------------------------------------------------------
> [INFO]
> [INFO] --- maven-release-plugin:2.3.2:perform (default-cli) @
> wicket-native-websocket-core ---
> [ERROR] No SCM URL was provided to perform the release from
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Wicket Native WebSocket Core ...................... FAILURE [ 0.471 s]
> [INFO] Wicket Native WebSocket Jetty ..................... SKIPPED
> [INFO] Wicket Native WebSocket Jetty 9 ................... SKIPPED
> [INFO] Wicket Native WebSocket Tomcat 7.x ................ SKIPPED
> [INFO] Wicket Common Tests ............................... SKIPPED
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 1.467 s
> [INFO] Finished at: 2014-04-16T00:36:49+01:00
> [INFO] Final Memory: 18M/81M
> [INFO]
> ------------------------------------------------------------------------
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
