Continuum

Build Definition settings are either misleading or wrong

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.0
  • Fix Version/s: 1.0.1
  • Component/s: Web interface
  • Labels:
    None
  • Complexity:
    Intermediate
  • Number of attachments :
    0

Description

Steps to reproduce:

1. Navigate to the project's information page. Under "Build Definitions", click "Edit".
2. Change the goals for the project.
3. Leave the checkbox "Check it if it's the default build definition" checked.
4. Save changes.
5. Add a new project. Note that it will /not/ pick up the new goals you just entered.

Basically, I think this item is worded strangely. Does it mean you want the project to USE the default build definition, or are you CHANGING the default build definition? If the latter, it's broken; if the former, where /can/ I change the default build goals?

A possibly related issue: should the pom.xml's <defaultGoal/> field be used initially?

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Emmanuel Venisse added a comment -

a default build definition is the definition used when you clcik on build button in summary page.

Show
Emmanuel Venisse added a comment - a default build definition is the definition used when you clcik on build button in summary page.
Hide
Permalink
Emmanuel Venisse added a comment -

I added more explanations in message of "Check if it's default build definiton"
We used now defaultGoal if it's defined in pom

Show
Emmanuel Venisse added a comment - I added more explanations in message of "Check if it's default build definiton" We used now defaultGoal if it's defined in pom

People

Vote (0)
Watch (0)

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.