jira.codehaus.org

  • Log In Access more options
    • Online Help
    • Keyboard Shortcuts
    • About JIRA
    • JIRA Credits
    • What?s New
  • Dashboards Access more options (Alt+d)
  • Projects Access more options (Alt+p)
  • Issues Access more options (Alt+i)
Signup
Maven 1.x CruiseControl Plugin
  • Maven 1.x CruiseControl Plugin
  • MPCRUISECONTROL-18

Maven properties to control plugin

  • Log In
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: Improvement Improvement
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 1.6
  • Fix Version/s: None
  • Labels:
    None
  • Number of attachments :
    0

Description

We need a mechanism to pass parameters to the jvm started by the cruisecontrol maven plgin jelly script.

The parameters in question are -Djava.awt.headless=true and -port=9090 (to instanatiate the JMX server).

If these could be maven plugin properties then we could specify them in the local build.properties that would be fantastic.

Activity

Ascending order - Click to sort in descending order
  • All
  • Comments
  • Work Log
  • History
  • Activity
Hide
Permalink
David Eric Pugh added a comment - 17/Mar/05 5:21 AM

I get the port parameter, and I could buy adding the -configfile parameter. But why do you need to pass the headless argument?

I run CC on linux and don't have any issues with it. Patches are welcome.

Also, I am not sure that cruisecontrol:run should be your primary way of starting up Cruisecontrol. It maybe, though I am not certain, that the intent is to provide a way to test your config file by starting up CC and seeing if it validates everything.

Show
David Eric Pugh added a comment - 17/Mar/05 5:21 AM I get the port parameter, and I could buy adding the -configfile parameter. But why do you need to pass the headless argument? I run CC on linux and don't have any issues with it. Patches are welcome. Also, I am not sure that cruisecontrol:run should be your primary way of starting up Cruisecontrol. It maybe, though I am not certain, that the intent is to provide a way to test your config file by starting up CC and seeing if it validates everything.
Hide
Permalink
David Eric Pugh added a comment - 22/Jun/05 6:55 AM

Vincent,

I think cruisecontrol-run was your inspiration. Do you mind discussing how you use it? I am assuming as a shortcut for debugging your configuration file, versus as your standard way of running CC? There are some other properties that should propbably be added by default like the rmiport as well. Additionally, with the new Jetty bundled version, maybe we would want to use that instead?

Show
David Eric Pugh added a comment - 22/Jun/05 6:55 AM Vincent, I think cruisecontrol-run was your inspiration. Do you mind discussing how you use it? I am assuming as a shortcut for debugging your configuration file, versus as your standard way of running CC? There are some other properties that should propbably be added by default like the rmiport as well. Additionally, with the new Jetty bundled version, maybe we would want to use that instead?
Hide
Permalink
Jamie Bisotti added a comment - 30/Jun/05 12:02 PM

Why couldn't (shouldn't) it be the standard way of running CC? You have to seed CC's checkout directory anyway, why not go a step, or two, further and use that seeded code to run cruisecontrol:configure, for each seeded project (assuming all projects point to the same config.xml) and then do a cruisecontrol:run to kick things off? I think that would be ideal.

Show
Jamie Bisotti added a comment - 30/Jun/05 12:02 PM Why couldn't (shouldn't) it be the standard way of running CC? You have to seed CC's checkout directory anyway, why not go a step, or two, further and use that seeded code to run cruisecontrol:configure, for each seeded project (assuming all projects point to the same config.xml) and then do a cruisecontrol:run to kick things off? I think that would be ideal.
Hide
Permalink
Vincent Massol added a comment - 30/Jun/05 3:33 PM

Hi David,

I don't really use CC ATM. I've created it because I thought it was missing. If properties are missing they should be added. I just implemented a first version. I'm not aware of the "new Jetty bundled version" but maybe there's a better way of doing it? What I think is nice is the ability to start it from the Maven build.

It has always bothered me that CC was started as a command line deamon and that you need a separate reporting webapp. Look at luntbuild which has everything in one. Much easier. Maybe the new "jetty bundled" stuff is meant to do that?

Show
Vincent Massol added a comment - 30/Jun/05 3:33 PM Hi David, I don't really use CC ATM. I've created it because I thought it was missing. If properties are missing they should be added. I just implemented a first version. I'm not aware of the "new Jetty bundled version" but maybe there's a better way of doing it? What I think is nice is the ability to start it from the Maven build. It has always bothered me that CC was started as a command line deamon and that you need a separate reporting webapp. Look at luntbuild which has everything in one. Much easier. Maybe the new "jetty bundled" stuff is meant to do that?

People

  • Assignee:
    Unassigned
    Reporter:
    Brendan Donovan
Vote (0)
Watch (0)

Dates

  • Created:
    27/Jan/05 2:23 AM
    Updated:
    30/Jun/05 3:33 PM
  • Atlassian JIRA (v5.2.7#850-sha1:b2af0c8)
  • Report a problem
  • Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.