[
https://jira.codehaus.org/browse/MRELEASE-814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=316397#comment-316397
]
Fred Cooke commented on MRELEASE-814:
-------------------------------------
Having the EXACT same property in the parent and the child project results in
success too. I think it should be clear that this is inconsistent/hard-coded
behaviour given the fact that the field contents are identical and the results
different.
http://maven.apache.org/pom.html#SCM No contact of arbitrary modifications
mentioned here.
I guess MVN + Git is still pretty new. :-(
As a temporary workaround I'm going to add the (exact same identical) SCM
information to each child POM. I hope I can revert this needless duplication at
some point in the not too distant future.
Maven itself seems to be under git now, when are the various plugins scheduled
for migration? And/or how does one gain SVN commit access to something like the
maven release plugin?
> Property interpolation of developerConnection broken when inheritting from
> parent
> ---------------------------------------------------------------------------------
>
> Key: MRELEASE-814
> URL: https://jira.codehaus.org/browse/MRELEASE-814
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: Git, prepare
> Affects Versions: 2.0, 2.3.2, 2.4
> Environment: Debian Linux OpenJDK 7 mvn 3.0.4
> Reporter: Fred Cooke
> Priority: Blocker
> Attachments: demo.project.git.release.bug.tgz
>
>
> If developerConnection is setup like this in a parent and inherited:
> <developerConnection>scm:git:git:${project.groupId}/${project.artifactId}.git</developerConnection>
> Then the Git SCM URL is incorrect when attempting to do a release:prepare
> (and perhaps other operations)
> In the example project that I've included this is what it tries to do:
> [INFO] Executing: /bin/sh -c cd /home/fred/workspace/ShouldSeeThisOnceOnly &&
> git push git:com.example/ShouldSeeThisOnceOnly.git/ShouldSeeThisOnceOnly
> master:master
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-release-plugin:2.4:prepare (default-cli) on
> project ShouldSeeThisOnceOnly: Unable to commit files
> [ERROR] W access for
> com.example/ShouldSeeThisOnceOnly.git/ShouldSeeThisOnceOnly DENIED to fred
> I've used this same method with the property directly in the project POM with
> success. It seems that having it in the parent is the issue.
> Note, .ssh/config setup is required for a URL of this nature:
> host git
> user git
> hostname localhost
> port 22
> identityfile ~/.ssh/id_rsa
> Change these, and the deploy details to suit yourself.
> I sincerely hope that I'm doing something stupid and that this is not a bug
> as I desperately need to do some releases and waiting for a fix wouldn't be
> ideal, nor would hacking what should be inherited into each POM. Sadly, I
> doubt that I'm wrong this time, as I copy pasted the exact contents from my
> bogus parent into my pom, removed the parent ref, and it works as expected.
> This seems like an ugly hangover from SVN usage to me.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
