[
http://jira.codehaus.org/browse/MRELEASE-272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185297#action_185297
]
Olivier Lamy commented on MRELEASE-272:
---------------------------------------
Can you reproduce this with last version (2.0-beta-9) ?
> Release plugin tags into wrong directory
> ----------------------------------------
>
> Key: MRELEASE-272
> URL: http://jira.codehaus.org/browse/MRELEASE-272
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: scm
> Affects Versions: 2.0-beta-4, 2.0-beta-6
> Environment: osx 10.4, java 5
> Reporter: David Jencks
>
> I tried to use the release plugin, both beta-6 and beta-4 to release some
> new geronimo jars, but it kept tagging into a parent poms directory, not the
> one specified in the scm element OR one specified on the command line via
> -DtagBase. To see this
> svn co -r561686
> https://svn.apache.org/repos/asf/geronimo/components/txmanager/trunk
> mvn release:prepare -DdryRun=true
> -DtagBase=https://svn.apache.org/repos/asf/geronimo/components/txmanager
> cat pom.xml.tag
> The parent pom does not have a scm section. Would that help? As I write it
> is not yet released, for simplicity you may want to check it out from
> svn co https://svn.apache.org/repos/asf/geronimo/genesis/branches/1.2
> the release plugin version specified there is 2.0-beta-4 but changing it to
> beta-6 has no apparent effect.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
