The issue I was referring to was this one : https://jira.codehaus.org/browse/MRELEASE-581
Arnaud On Sat, Jul 27, 2013 at 9:49 PM, Robert Scholte <[email protected]>wrote: > Hi, > > From which location are you releasing, from master or from jrobocom-parent? > > If it's the first, then the scm section should be placed here. > If it's the latter, I think your scm-connections are wrong(not sure) and > you must use m-release-p 2.3.2 due to the SCM-709 issue. > > Robert > > > Op Sat, 27 Jul 2013 21:35:48 +0200 schreef <[email protected]>: > > > Thank you Robert >> I tried MRP 2.3.2 and i got the exact same result. I also have the same >> setup referenced in the OP's comment on the accepted answer (aggregator >> inherits from parent, parent is a submodule of aggregator and actual code >> modules depend on their sibling parent) but somehow it doesn't work for me. >> The only difference i see is git. >> >> Arnaud, in the SO question referenced by Robert and in the blog post >> referenced in it at least 2 other people managed to make it work with an >> explicit relative path. Here is the referenced blog >> http://warpedjavaguy.**wordpress.com/2011/08/08/how-** >> i-defeated-the-maven-release-**plugin-in-a-flat-structured-** >> multi-module-project/<http://warpedjavaguy.wordpress.com/2011/08/08/how-i-defeated-the-maven-release-plugin-in-a-flat-structured-multi-module-project/> >> i'm sure adding git submodules makes everything much more complex. This >> is why i'm surprised mine doesn't work, my setup is very vanilla so i'm >> sure there's hundreds of people trying to do the same thing >> >> Thanks for your help >> >> Any other ideas? >> >> i would still like to know why the push url contains the artifactId of >> the aggregator. I'm not sure if this is MRP or the scm plugin's doing >> >> >> >> -----"Robert Scholte" <[email protected]> wrote: ----- >> To: "Maven Users List" <[email protected]> >> From: "Robert Scholte" <[email protected]> >> Date: 07/27/2013 12:29PM >> Subject: Re: maven-release-plugin with github project >> >> http://stackoverflow.com/**questions/17766247/maven-** >> release-plugin-pushing-tags-**to-wrong-repo/17771493#**17771493<http://stackoverflow.com/questions/17766247/maven-release-plugin-pushing-tags-to-wrong-repo/17771493#17771493> >> will help you. >> >> Robert >> >> Op Sat, 27 Jul 2013 18:13:28 +0200 schreef <[email protected]>: >> >> >>> >>> I'm trying to release a multimodule maven project cloned in github. My >>> project has the parent pom as a submodule of the root aggregator. if i run >>> the release in dryRun mode it works fine, however if I run it for real this >>> is what i get near the end >>> >>> >>> ... >>> [INFO] Checking in modified POMs... >>> [INFO] Executing: /bin/sh -c cd "/home/hilikus/dev/Eclipse >>> workspace/JRoboCom" && git add -- jrobocom-parent/pom.xml >>> jrobocom-core/pom.xml jrobocom-simple-gui/pom.xml jrobocom-samples/pom.xml >>> jrobocom-samples/legends/pom.**xml jrobocom-samples/simple/pom.**xml >>> jrobocom-samples/simple/**4Lunch/pom.xml >>> jrobocom-samples/simple/black-**jacks/pom.xml >>> jrobocom-samples/simple/bank-**jumper/pom.xml pom.xml >>> [INFO] Working directory: /home/hilikus/dev/Eclipse workspace/JRoboCom >>> [INFO] Executing: /bin/sh -c cd "/home/hilikus/dev/Eclipse >>> workspace/JRoboCom" && git status >>> [INFO] Working directory: /home/hilikus/dev/Eclipse workspace/JRoboCom >>> [INFO] Executing: /bin/sh -c cd "/home/hilikus/dev/Eclipse >>> workspace/JRoboCom" && git commit --verbose -F /tmp/maven-scm-646807004. >>> **commit jrobocom-parent/pom.xml jrobocom-core/pom.xml >>> jrobocom-simple-gui/pom.xml jrobocom-samples/pom.xml >>> jrobocom-samples/legends/pom.**xml jrobocom-samples/simple/pom.**xml >>> jrobocom-samples/simple/**4Lunch/pom.xml >>> jrobocom-samples/simple/black-**jacks/pom.xml >>> jrobocom-samples/simple/bank-**jumper/pom.xml pom.xml >>> [INFO] Working directory: /home/hilikus/dev/Eclipse workspace/JRoboCom >>> [INFO] Executing: /bin/sh -c cd "/home/hilikus/dev/Eclipse >>> workspace/JRoboCom" && git symbolic-ref HEAD >>> [INFO] Working directory: /home/hilikus/dev/Eclipse workspace/JRoboCom >>> [INFO] Executing: /bin/sh -c cd "/home/hilikus/dev/Eclipse >>> workspace/JRoboCom" && git push https://github.com/theHilikus/** >>> JRoboCom.git/jrobocom-**aggregator<https://github.com/theHilikus/JRoboCom.git/jrobocom-aggregator>master:master >>> [INFO] Working directory: /home/hilikus/dev/Eclipse workspace/JRoboCom >>> [INFO] ------------------------------**------------------------------** >>> ------------ >>> [INFO] Reactor Summary: >>> [INFO] >>> [INFO] Parent POM ..............................**.......... SKIPPED >>> ... >>> [INFO] Bank-jumper ..............................**......... SKIPPED >>> [INFO] The overall aggregator ............................ FAILURE >>> [3:30.447s] >>> [INFO] ------------------------------**------------------------------** >>> ------------ >>> [INFO] BUILD FAILURE >>> [INFO] ------------------------------**------------------------------** >>> ------------ >>> [INFO] Total time: 3:32.658s >>> [INFO] Finished at: Tue Jul 23 22:31:43 EDT 2013 >>> [INFO] Final Memory: 9M/44M >>> [INFO] ------------------------------**------------------------------** >>> ------------ >>> [ERROR] Failed to execute goal org.apache.maven.plugins:** >>> maven-release-plugin:2.4.1:**prepare (default-cli) on project >>> jrobocom-aggregator: Unable to commit files >>> [ERROR] Provider message: >>> [ERROR] The git-push command failed. >>> [ERROR] Command output: >>> [ERROR] fatal: https://github.com/theHilikus/**JRoboCom.git/jrobocom-** >>> aggregator/info/refs<https://github.com/theHilikus/JRoboCom.git/jrobocom-aggregator/info/refs>not >>> found: did you run git update-server-info on the server? >>> [ERROR] -> [Help 1] >>> >>> >>> If I run that same git push command by hand it does give me that error, >>> however, if i run the push with the url just up to .git and remove the >>> /jrobocom-aggregator it works fine >>> >>> Where does the MRP take the push url from? i'm running mvn from the >>> root aggregator since i want to release all submodules together but i >>> don't see why the push url should include the aggregator's artifact id >>> >>> What am i doing wrong? this seems like the canonical release procedure >>> >>> This is the aggregator POM (before running the release) in case anyone >>> is interested https://github.com/theHilikus/** >>> JRoboCom/blob/master/pom.xml<https://github.com/theHilikus/JRoboCom/blob/master/pom.xml> >>> and from there you can find all the other poms >>> >>> Thank you, >>> DISCLAIMER: >>> Privileged and/or Confidential information may be contained in this >>> message. If you are not the addressee of this message, you may not >>> copy, use or deliver this message to anyone. In such event, you >>> should destroy the message and kindly notify the sender by reply >>> e-mail. It is understood that opinions or conclusions that do not >>> relate to the official business of the company are neither given >>> nor endorsed by the company. >>> Thank You. >>> >> >> ------------------------------**------------------------------**--------- >> To unsubscribe, e-mail: >> users-unsubscribe@maven.**apache.org<[email protected]> >> For additional commands, e-mail: [email protected] >> >> >> DISCLAIMER: >> Privileged and/or Confidential information may be contained in this >> message. If you are not the addressee of this message, you may not >> copy, use or deliver this message to anyone. In such event, you >> should destroy the message and kindly notify the sender by reply >> e-mail. It is understood that opinions or conclusions that do not >> relate to the official business of the company are neither given >> nor endorsed by the company. >> Thank You. >> > > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: > users-unsubscribe@maven.**apache.org<[email protected]> > For additional commands, e-mail: [email protected] > > -- ----- Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier
