From: Florian G. (JIRA) <ji...@us...> - 2009-03-29 12:21:48
|
[ http://jira.public.thoughtworks.org/browse/CC-904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Florian Gilcher updated CC-904: ------------------------------- Attachment: RakeScript.patch > Environment-independent RakeBuilder > ----------------------------------- > > Key: CC-904 > URL: http://jira.public.thoughtworks.org/browse/CC-904 > Project: CruiseControl > Issue Type: Improvement > Components: Core Application > Reporter: Florian Gilcher > Assigned To: Dan Rollo > Priority: Minor > Attachments: RakePatch.patch, RakeScript.patch, RakeScriptTest.2.patch, RakeScriptTest.patch > > > RakeBuilder and RakeScript expect "rake" to be the right executable to run raketasks. Now that Ruby 1.9 and JRuby are out in the wild, this is not necessarily true. (could be called ruby19, rake19, etc.) > This patch makes the Ruby executable and the Rake executable configurable. > Adds to parameters "rubyExecutable" and "rakeExecutable" with default values "ruby" and "rake". Also changes RubyScript to execute "rubyexecutable -S rakeexecutable", which is the portable way to do. > Also changes the default rakefile name to "Rakefile", which is the common name 99% of Ruby projects use. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.public.thoughtworks.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |