continuum-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dieter Joho (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (CONTINUUM-2449) Continuum Release ignores scm configuration
Date Sat, 30 Jan 2010 12:03:55 GMT

    [ http://jira.codehaus.org/browse/CONTINUUM-2449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208666#action_208666
] 

Dieter Joho commented on CONTINUUM-2449:
----------------------------------------

Thanks for the help.

Our project situation is a bit different than yours. The project structure is maybe a bit
uncommon. Therefore I am not sure whether this is a bug or not. I just reported it as the
behavior from continuum and maven release plugin is different.

Project structure:
{quote}/trunk/mainproject/nonmavenproject
/trunk/mainproject/mavenproject/pom.xml
/trunk/mainproject/mavenproject/mavenmodule1/pom.xml
/trunk/mainproject/mavenproject/mavenmodule2/pom.xml{quote}

/trunk/mainproject/mavenproject/pom.xml is the registered SCM URL in Continuum, whereas the
scm configuration in this pom.xml is 
{quote}<scm>
<connection>scm:svn:http://xxx/svn/testproject/trunk/</connection>
<developerConnection>scm:svn:http://xxx/svn/testproject/trunk/</developerConnection>
<url>http://xxx/viewvc/testproject/trunk/</url>
</scm>{quote}

Releasing from within Continuum creates the tag from the registered SCM URL and not from the
scm configuration within the pom.xml

Continuum tag is from /trunk/mainproject/mavenproject/
Release plugin tag is from /trunk/mainproject/

As a solution to my problem I created a dummy pom.xml in /trunk/mainproject/ and registered
this in Continuum. Therefore now we have a proper tag.

If this mixing of maven and non-maven projects within the same repository "project" is not
supported, then this issue can be closed.

Thanks for the help



> 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

        

Mime
View raw message