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...@grassvalley.com on 2014/10/24 16:58:34 UTC
release of git folder
Hi guys, now that https://jira.codehaus.org/browse/MRELEASE-875 has been
fixed we are trying to release from a non-root module in a git repo but
encounter a problem at the git push stage of release:prepare. The url for
the git repo where it tries to push is wrong. Maven is appending the name
of the submodule's artifactId to the path of developerConnection that it
inherited from its parent; this behaviour was fine when we were in CVS,
but now in git it doesn't make sense. I found some people on SO (
http://stackoverflow.com/questions/6727450/releasing-a-multi-module-maven-project-with-git
) having the same issue but none of the workarounds I tried work.
Is there an official fix or workaround for this?
we're using maven 3.0.4 and m-release-p 2.5.1
Thank you,
Alejandro Endo | Software Designer/Concepteur de logiciels
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: release of git folder
Posted by Robert Scholte <rf...@apache.org>.
AFAIK it has always been like this since the first Maven 2 releases.
And it's not just both the connections, but also the siteURL.
So maybe they have the same symptoms, but I think it is a different issue.
Robert
Op Tue, 28 Oct 2014 15:01:45 +0100 schreef
<Al...@grassvalley.com>:
> Mark, we are using maven 3.0.4 and encounter the same issue, it must have
> been introduced before
>
> Alejandro Endo | Software Designer/Concepteur de logiciels
>
>
>
>
>
> From: "Mark Derricutt" <ma...@talios.com>
> To: "Maven Users List" <us...@maven.apache.org>,
> Date: 2014-10-27 17:50
> Subject: Re: release of git folder
>
>
>
> On 25 Oct 2014, at 23:05, Robert Scholte wrote:
>
>> the only workaround I can think of is specifying the developerConnection
> in this project as well.
>
> I was meaning to post about this bug the other week - which we came
> across
> when working on the tiles-maven-plugin - this was introduced in the
> DefaultInheritanceAssemble somewhere in 3.1.x cycle.
>
> For some reason - for every parent in the chain it appends the artifactId
> to the parents SCM section fields ( connection, developerConnection etc.
> ).
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: release of git folder
Posted by Al...@grassvalley.com.
Mark, we are using maven 3.0.4 and encounter the same issue, it must have
been introduced before
Alejandro Endo | Software Designer/Concepteur de logiciels
From: "Mark Derricutt" <ma...@talios.com>
To: "Maven Users List" <us...@maven.apache.org>,
Date: 2014-10-27 17:50
Subject: Re: release of git folder
On 25 Oct 2014, at 23:05, Robert Scholte wrote:
> the only workaround I can think of is specifying the developerConnection
in this project as well.
I was meaning to post about this bug the other week - which we came across
when working on the tiles-maven-plugin - this was introduced in the
DefaultInheritanceAssemble somewhere in 3.1.x cycle.
For some reason - for every parent in the chain it appends the artifactId
to the parents SCM section fields ( connection, developerConnection etc.
).
--
Mark Derricutt
http://www.theoryinpractice.net
http://plus.google.com/+MarkDerricutt
http://twitter.com/talios
http://facebook.com/mderricutt
[attachment "signature.asc" deleted by Alejandro
Endo/MontrealMIR/BeldenCDT]
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: release of git folder
Posted by Mark Derricutt <ma...@talios.com>.
On 25 Oct 2014, at 23:05, Robert Scholte wrote:
> the only workaround I can think of is specifying the developerConnection in this project as well.
I was meaning to post about this bug the other week - which we came across when working on the tiles-maven-plugin - this was introduced in the DefaultInheritanceAssemble somewhere in 3.1.x cycle.
For some reason - for every parent in the chain it appends the artifactId to the parents SCM section fields ( connection, developerConnection etc. ).
--
Mark Derricutt
http://www.theoryinpractice.net
http://plus.google.com/+MarkDerricutt
http://twitter.com/talios
http://facebook.com/mderricutt
Re: release of git folder
Posted by Al...@grassvalley.com.
That's what we figured...
we were trying to not pollute our hundreds of poms with the exact same
declaration of the scm
Thank you Robert
Alejandro Endo | Software Designer/Concepteur de logiciels
Grass Valley, A Belden Brand | Tel: (514) 333-1772 Ext: 3789
3499 Douglas-B.-Floreani, St-Laurent, Quebec Canada H4S 2C6
From: "Robert Scholte" <rf...@apache.org>
To: "Maven Users List" <us...@maven.apache.org>,
Date: 2014-10-25 06:05
Subject: Re: release of git folder
Hi,
the only workaround I can think of is specifying the developerConnection
in this project as well.
The root cause of appending the artifactId to the inherited connection is
in Maven Core, where as it should actually be SCM independent. That's a
huge change with a huge impact. It requires a lot plugins to be prepared
for that.
So as said: always specify the developerConnection in you release root
project.
thanks,
Robert
Op Fri, 24 Oct 2014 16:58:34 +0200 schreef
<Al...@grassvalley.com>:
> Hi guys, now that https://jira.codehaus.org/browse/MRELEASE-875 has been
> fixed we are trying to release from a non-root module in a git repo but
> encounter a problem at the git push stage of release:prepare. The url
for
> the git repo where it tries to push is wrong. Maven is appending the
name
> of the submodule's artifactId to the path of developerConnection that it
> inherited from its parent; this behaviour was fine when we were in CVS,
> but now in git it doesn't make sense. I found some people on SO (
>
http://stackoverflow.com/questions/6727450/releasing-a-multi-module-maven-project-with-git
> ) having the same issue but none of the workarounds I tried work.
>
> Is there an official fix or workaround for this?
> we're using maven 3.0.4 and m-release-p 2.5.1
>
>
> Thank you,
>
> Alejandro Endo | Software Designer/Concepteur de logiciels
>
> 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: release of git folder
Posted by Robert Scholte <rf...@apache.org>.
Hi,
the only workaround I can think of is specifying the developerConnection
in this project as well.
The root cause of appending the artifactId to the inherited connection is
in Maven Core, where as it should actually be SCM independent. That's a
huge change with a huge impact. It requires a lot plugins to be prepared
for that.
So as said: always specify the developerConnection in you release root
project.
thanks,
Robert
Op Fri, 24 Oct 2014 16:58:34 +0200 schreef
<Al...@grassvalley.com>:
> Hi guys, now that https://jira.codehaus.org/browse/MRELEASE-875 has been
> fixed we are trying to release from a non-root module in a git repo but
> encounter a problem at the git push stage of release:prepare. The url for
> the git repo where it tries to push is wrong. Maven is appending the name
> of the submodule's artifactId to the path of developerConnection that it
> inherited from its parent; this behaviour was fine when we were in CVS,
> but now in git it doesn't make sense. I found some people on SO (
> http://stackoverflow.com/questions/6727450/releasing-a-multi-module-maven-project-with-git
> ) having the same issue but none of the workarounds I tried work.
>
> Is there an official fix or workaround for this?
> we're using maven 3.0.4 and m-release-p 2.5.1
>
>
> Thank you,
>
> Alejandro Endo | Software Designer/Concepteur de logiciels
>
> 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