[
http://jira.codehaus.org/browse/MRELEASE-325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=187066#action_187066
]
Michael Wenig edited comment on MRELEASE-325 at 8/14/09 3:51 AM:
-----------------------------------------------------------------
MRELEASE-128 contains a patch which solves this problem (at least at our site)
was (Author: micha123):
Here is a patch which solves this problem (at least at our site)
> The release plugin does not keep the variable substitution in the
> connection/developer url after a release prepare/perform.
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: MRELEASE-325
> URL: http://jira.codehaus.org/browse/MRELEASE-325
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.0-beta-7
> Environment: All OSes, Maven 2.0.8
> Reporter: Oskar Carlstedt
>
> The release plugin does not keep the variable substitution in the connection
> url after a release prepare/perform. A short example:
> SCM Url: scm:svn:${scm.baseurl}/myproject/trunk
> A property: <scm.baseurl>svn+ssh://svn.mydomain.com/therepo</scm.baseurl>
> After running the release plugin I get a new SCM url:
> SCM Url: scm:svn:svn+ssh://svn.mydomain.com/therepo/myproject/trunk
> Is it possible to keep the original url. If I want to change our svn url then
> I must go through all our projects and that is not a very good idea.
> Thanks in advance
> /Oskar
--
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
