Ok, removing the dependency to the parent in the aggregator seemed to fix the problem. now the push url makes sense: git push https://github.com/theHilikus/JRoboCom.git master:master
However, now I encounter a problem i've always had in the past when releasing and never bothered to troubleshoot. After running git push I am asked for the username and pass of github. After I enter them, the release just hangs there This is the output using -X ... [INFO] Executing: /bin/sh -c cd "/home/hilikus/dev/Eclipse workspace/JRoboCom" && git commit --verbose -F /tmp/maven-scm-1784899634.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 master:master [INFO] Working directory: /home/hilikus/dev/Eclipse workspace/JRoboCom Username for 'https://github.com': theHilikus Password for 'https://[email protected]': //hangs here forever after i press enter the only way i have been able to fix this is by cancelling the release (ctrl-c), running "git push https://github.com/theHilikus/JRoboCom.git master:master" by hand (no maven) which completes without a problem, then undoing the manual push and then rerunning the release-plugin, which now doesn't block after i enter my credentials; pretty annoying and long procedure. Any ideas what could be wrong this time? Thanks again, Alejandro -----"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 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 > 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 > 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ÿÿ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: [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.
