continuum-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Edd Steel (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (CONTINUUM-548) Can't change project name
Date Thu, 11 Dec 2008 09:12:19 GMT

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

Edd Steel commented on CONTINUUM-548:
-------------------------------------

The POM name refers to the project, but if, as in our case, you have two branches of the code
being built, you need the name in continuum to reflect that.
Since we are using perforce as the SCM, the branches are just two different directories.

As it is, inside the project group we have two projects: "Product" and "Product". What we
want is "Product - trunk" and "Product - 1.3 branch". There isn't a way to achieve this currently,
as both should share the same build definition. Changing the POM's name to add trunk doesn't
make a lot of sense.

You can tell the difference between the projects in continuum's admin screens because of the
version number, but build failure emails are particularly opaque.

> Can't change project name
> -------------------------
>
>                 Key: CONTINUUM-548
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-548
>             Project: Continuum
>          Issue Type: Bug
>          Components: Core system
>    Affects Versions: 1.0.2
>            Reporter: Tim McCune
>            Assignee: Olivier Lamy
>             Fix For: 1.1-alpha-1
>
>
> I have created a new Maven 1.x project in Continuum and after doing so, edited its project
name in the web UI.  The edit seems to work fine, but the next time the project gets built,
its name gets reverted back to the original name that it picked up from the POM.  This is
a real pain in the ass because I want multiple Continuum projects created from the same POM
(so they are all getting the same name) to do things like building multiple branches, and
running different goals on different schedules.

-- 
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