Gaven maven release plugin not working in subfolders

We have a problem with the maven-release plugin with git and maven-modules.

We have the following project structure:

pom.xml(ApplicationTest and ApplicationConf are modules)

ApplicationWeb

---pom.xml(parent pom in root folder)

ApplicationTest

---pom.xml(parent pom in root folder)

ApplicationConf

---pom.xml(All environments are modules. This has no parent pom)

---ConfDev

-------pom.xml(parent ApplicationConf)

---ConfTst

-------pom.xml(parent ApplicationConf)

---ConfAcc

-------pom.xml(parent ApplicationConf)

---ConfPrd

-------pom.xml(parent ApplicationConf)

Now we like to release dev config (Parent is already released). This is by issuing the maven release at ApplicationConf / ConfDev / pom.xml.

Now, the preparation for the release fails because it uses the wrong git URL when it wants to push the changed. It attaches the identifier of the pom artifact, which we would like to release on the git url.

http://gitrepourl/git_repo.git/artifact-id

We defined scm parameters in pom in ApplicationConf so that the root of all environments.

<scm>
  <developerConnection>scm:git:http://gitrepourl/git_repo.git</developerConnection>
</scm>

Do we have the wrong project structure, the wrong setup, or is this a bug in the maven-release plugin?

Used Version:

maven-release-plugin 2.3.2 and 2.4.1

Maven 3.0.5

Possible Solution:

config pom config pom more scm, :

<scm>
<url>https://github.com/XXX/YYY</url>
<connection>scm:git:ssh://git@github.com/XXX/YYY.git</connection>
<developerConnection>scm:git:ssh://git@github.com/XXX/YYY.git</developerConnection>

. ?

+4

All Articles