continuum-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brett Porter (JIRA)" <>
Subject [jira] Updated: (CONTINUUM-250) Continuum should not update SCM url for Maven1 projects.
Date Wed, 22 Apr 2009 15:21:45 GMT


Brett Porter updated CONTINUUM-250:

    Fix Version/s: 1.x

> Continuum should not update SCM url for Maven1 projects.
> --------------------------------------------------------
>                 Key: CONTINUUM-250
>                 URL:
>             Project: Continuum
>          Issue Type: Bug
>          Components: Core system, SCM
>            Reporter: Tomasz Pik
>             Fix For: 1.x
> I've some Maven1 projects with parametrized SCM urls, in form of
> scm:cvs:pserver:${scm1.server}:/root/to/repo:module
> They are correct for Maven1 - SCM plugin works with them very good.
> Continuum do not handle them as there's no way to specify value for ${scm1.server} property
(and I think it's OK).
> Continnum loads evaluated project.xml (with ${scm1.server} replaced by correct value)
and starts building peoject but after checkout updates in internals (ContinuumProject) value
for SCM url with one from project.xml
> so in next build SCM url is invalid.
> As a resolution for this I'd like to propose:
> 1. add an option to import Maven1 project using SCM url only (and read rest of properties
from loaded POM) so user may provide evaluated version (this is a good thing to be done in
plugin for Maven1)
> 2. do not update ContiuumProject.scmURL based on POM;

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message