[ https://jira.codehaus.org/browse/MRELEASE-814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=317244#comment-317244 ]
Robert Scholte commented on MRELEASE-814: ----------------------------------------- Commit by project is supported: [prepare#commitByProject|http://maven.apache.org/maven-release/maven-release-plugin/prepare-mojo.html#commitByProject] Tag by project is a feature request: MRELEASE-241 I do understand this request, since if you tag a multimodule project, for all modules you need to know the name of the root-project to get to the tagged sources. (And yes I'm talking svn/cvs right now and assuming you're just browsing based on the tags-folder). > 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: Critical > Attachments: demo.project.git.release.bug.tgz > > > If {{developerConnection}} is setup like this in a parent and inherited: > {code:xml} > <developerConnection>scm:git:git:${project.groupId}/${project.artifactId}.git</developerConnection> > {code} > 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: > {noformat} > [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 > {noformat} > 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: > {noformat} > host git > user git > hostname localhost > port 22 > identityfile ~/.ssh/id_rsa > {noformat} > 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