Continuum

Can't change project name

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.0.2
  • Fix Version/s: 1.1-alpha-1
  • Component/s: Core system
  • Labels:
    None
  • Complexity:
    Intermediate
  • Number of attachments :
    0

Description

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.

Issue Links

This issue relates to:
CONTINUUM-490 Multi-dependency build changes project name in the continuum web interface after attemped build Major Closed

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Dan Tran added a comment -

I totally agree, i ended up to create multiple shell project for this purpose.

Show
Dan Tran added a comment - I totally agree, i ended up to create multiple shell project for this purpose.
Hide
Permalink
Heikki Rauhala added a comment -

Same behaviour in 1.0.3. This is really annoying when using profiles, and all the projects automatically revert back to the pom name after a build.

Show
Heikki Rauhala added a comment - Same behaviour in 1.0.3. This is really annoying when using profiles, and all the projects automatically revert back to the pom name after a build.
Hide
Permalink
Heikki Rauhala added a comment -

Also applies for Maven 2.0+ projects

Show
Heikki Rauhala added a comment - Also applies for Maven 2.0+ projects
Hide
Permalink
Jesse McConnell added a comment -

http://www.nabble.com/project-group-shortcuts-tf2542431.html#a7083998

I wrote on this and think we have a solution to this, just need to get it implemented

Show
Jesse McConnell added a comment - http://www.nabble.com/project-group-shortcuts-tf2542431.html#a7083998 I wrote on this and think we have a solution to this, just need to get it implemented
Hide
Permalink
Olivier Lamy added a comment -

With project group feature, it's fixed.

Show
Olivier Lamy added a comment - With project group feature, it's fixed.
Hide
Permalink
Marc Lustig added a comment -

We are using Continuum-SNAPSHOT (on Linux) from 25/07/2008 and this annoying problem still persists.
We rename a project-name.
After running a build the name is overwritten automatically, even if the POM has not changed.

IMO, the renamed project-name should be persisted somewhere, so that it won't get overwritten, even if the POM has changed and fetched from the SCM-System.

Show
Marc Lustig added a comment - We are using Continuum-SNAPSHOT (on Linux) from 25/07/2008 and this annoying problem still persists. We rename a project-name. After running a build the name is overwritten automatically, even if the POM has not changed. IMO, the renamed project-name should be persisted somewhere, so that it won't get overwritten, even if the POM has changed and fetched from the SCM-System.
Hide
Permalink
Emmanuel Venisse added a comment -

Why don't you change the project name directly in your pom???

Show
Emmanuel Venisse added a comment - Why don't you change the project name directly in your pom???
Hide
Permalink
Edd Steel added a comment -

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.

Show
Edd Steel added a comment - 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.

People

Vote (2)
Watch (4)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.