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
<[email protected]>:
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: [email protected]
For additional commands, e-mail: [email protected]
