[
http://jira.codehaus.org/browse/CONTINUUM-2449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=207916#action_207916
]
Wendy Smoak commented on CONTINUUM-2449:
----------------------------------------
Can you please try the latest release, Continuum 1.3.5, and see if it behaves
the way you expect?
There have been many improvements in the release process in 1.3.x, including
respecting all the configuration of the release plugin in the project pom.
There are no plans for future 1.2.x releases.
> Continuum Release ignores scm configuration
> -------------------------------------------
>
> Key: CONTINUUM-2449
> URL: http://jira.codehaus.org/browse/CONTINUUM-2449
> Project: Continuum
> Issue Type: Bug
> Components: Release
> Affects Versions: 1.2.3
> Environment: Redhat Enterprise 5.4
> java 1.6.0_16
> maven 2.0.10
> svn 1.6.6
> Reporter: Dieter Joho
>
> We have a maven project (http://xxx/svn/main/trunk/mvnproject) in a
> subversion repository. The maven project is registered in Continuum with the
> scm url scm:svn:http://xxx/svn/main/trunk/mvnproject. The main pom.xml
> contains the following scm section {quote}
> <scm>
> <connection>scm:svn:http://xxx/svn/main/trunk/</connection>
>
> <developerConnection>scm:svn:http://xxx/svn/main/trunk/</developerConnection>
> <url>http://xxx/viewvc/main/trunk/</url>
> </scm>
> {quote}
> Releasing the mvnproject with the maven release plugin creates the tag from
> the trunk (http://xxx/svn/trunk) whereas releasing from Continuum creates the
> tag from the maven project url (http://xxx/svn/trunk/mvnproject).
> I expected that Continuum would behave like the mvn release plugin.
--
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
