: 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
: 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
, Quebec Canada H4S 2C6
From: Robert Scholte rfscho...@apache.org
To: Maven Users List users@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
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
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
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
