[ http://jira.codehaus.org/browse/MPCRUISECONTROL-18?page=comments#action_42214 ]
Jamie Bisotti commented on MPCRUISECONTROL-18: ---------------------------------------------- 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. > Maven properties to control plugin > ---------------------------------- > > Key: MPCRUISECONTROL-18 > URL: http://jira.codehaus.org/browse/MPCRUISECONTROL-18 > Project: maven-cruisecontrol-plugin > Type: Improvement > Versions: 1.6 > Reporter: Brendan Donovan > > > 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. -- 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 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
