You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Al...@miranda.com on 2013/07/27 18:13:28 UTC
maven-release-plugin with github project
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.
Re: maven-release-plugin with github project
Posted by Al...@miranda.com.
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://theHilikus@github.com':
//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" <rf...@apache.org> wrote: -----
To: "Maven Users List" <us...@maven.apache.org>
From: "Robert Scholte" <rf...@apache.org>
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 <Al...@miranda.com>:
>
>
> 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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
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.
[CAUTION: Suspicious URL content] Re: maven-release-plugin with github
project
Posted by Al...@miranda.com.
There seem to be some differences to my case. The bug says "It seems to think for some reason that I am at the root of my scm tree". In my case i AM in the root of my scm tree. Also, in his problem, the build fails on the git commit. in my case it fails on the git push after the commit succeeds. Some comments also mention it happens in windows/cygwin. I'm running mine in linux
-----Arnaud Héritier <ah...@gmail.com> wrote: -----
To: Maven Users List <us...@maven.apache.org>
From: Arnaud Héritier <ah...@gmail.com>
Date: 07/27/2013 04:16PM
Subject: [CAUTION: Suspicious URL content] Re: maven-release-plugin with github project
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 <rf...@apache.org>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 <Al...@miranda.com>:
>
>
> 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" <rf...@apache.org> wrote: -----
>> To: "Maven Users List" <us...@maven.apache.org>
>> From: "Robert Scholte" <rf...@apache.org>
>> 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 <Al...@miranda.com>:
>>
>>
>>>
>>> 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<us...@maven.apache.org>
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>> 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<us...@maven.apache.org>
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
-----
Arnaud H‚ritier
http://aheritier.net
Mail/GTalk: aheritier AT gmail DOT com
Twitter/Skype : aheritier
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.
Re: maven-release-plugin with github project
Posted by Robert Scholte <rf...@apache.org>.
I'll try to fix this with Mark for the next release. I think more and more
people will hit this issue.
Robert
Op Sat, 27 Jul 2013 22:15:33 +0200 schreef Arnaud Héritier
<ah...@gmail.com>:
> 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
> <rf...@apache.org>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 <Al...@miranda.com>:
>>
>>
>> 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" <rf...@apache.org> wrote: -----
>>> To: "Maven Users List" <us...@maven.apache.org>
>>> From: "Robert Scholte" <rf...@apache.org>
>>> 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
>>> <Al...@miranda.com>:
>>>
>>>
>>>>
>>>> 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<us...@maven.apache.org>
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>>> 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<us...@maven.apache.org>
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: maven-release-plugin with github project
Posted by Arnaud Héritier <ah...@gmail.com>.
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 <rf...@apache.org>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 <Al...@miranda.com>:
>
>
> 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" <rf...@apache.org> wrote: -----
>> To: "Maven Users List" <us...@maven.apache.org>
>> From: "Robert Scholte" <rf...@apache.org>
>> 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 <Al...@miranda.com>:
>>
>>
>>>
>>> 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<us...@maven.apache.org>
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>> 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<us...@maven.apache.org>
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
-----
Arnaud Héritier
http://aheritier.net
Mail/GTalk: aheritier AT gmail DOT com
Twitter/Skype : aheritier
[CAUTION: Suspicious URL content] Re: maven-release-plugin with github
project
Posted by Al...@miranda.com.
from the root of the project, which is the same level as the aggregator pom. But instead of putting the scm section there like you suggest, I just made the aggregator inherit from its submodule (jrobocom-parent). Maybe this is what's confusing the release plugin. i will try duplicating the SCM section on the aggregator (not great, DRY principle, but i need to be able to have a defined SCM on the code modules so I cannot just move the scm section from jrobocom-parent to jrobocom-aggregator)
-----"Robert Scholte" <rf...@apache.org> wrote: -----
To: "Maven Users List" <us...@maven.apache.org>
From: "Robert Scholte" <rf...@apache.org>
Date: 07/27/2013 03:49PM
Subject: [CAUTION: Suspicious URL content] Re: maven-release-plugin with github project
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 <Al...@miranda.com>:
> 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/
> 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" <rf...@apache.org> wrote: -----
> To: "Maven Users List" <us...@maven.apache.org>
> From: "Robert Scholte" <rf...@apache.org>
> 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 <Al...@miranda.com>:
>
>>
>>
>> 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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
> 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
For additional commands, e-mail: users-help@maven.apache.org
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.
Re: maven-release-plugin with github project
Posted by Robert Scholte <rf...@apache.org>.
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 <Al...@miranda.com>:
> 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/
> 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" <rf...@apache.org> wrote: -----
> To: "Maven Users List" <us...@maven.apache.org>
> From: "Robert Scholte" <rf...@apache.org>
> 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 <Al...@miranda.com>:
>
>>
>>
>> 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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
> 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
For additional commands, e-mail: users-help@maven.apache.org
Re: maven-release-plugin with github project
Posted by Al...@miranda.com.
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/
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" <rf...@apache.org> wrote: -----
To: "Maven Users List" <us...@maven.apache.org>
From: "Robert Scholte" <rf...@apache.org>
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 <Al...@miranda.com>:
>
>
> 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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
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.
Re: maven-release-plugin with github project
Posted by Robert Scholte <rf...@apache.org>.
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 <Al...@miranda.com>:
>
>
> 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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: maven-release-plugin with github project
Posted by Arnaud Héritier <ah...@gmail.com>.
Someone show me a similar issue with the release plugin in a project
using git where the parent/reactor is at the same level than modules
(moreover each modules where git submodules AFAIR )
The usage of relative path with in the reactor breaks the release.
There is an issue in Jira with a patch but AFAIR there was only the
code fix (no new test ..)
---------
Arnaud
Le 27 juil. 2013 à 18:14, "Alejandro.Endo@miranda.com"
<Al...@miranda.com> a écrit :
>
>
> 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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org