Hi, Thanks for your reply. I was able to set the system properties. I couldn't change the dependencies though as REQUIRES is a constant but now I know what has to be done to get this working much better. However, I haven't done anything with ruby ever before, so this is quite an adventure for me... But I'll try to make some patches eventually. Cannot make any promises of the deadline though.
It also looks like the Scala and Specs support needs some improvements. Like an option not to fork a new jvm for each spec. Best, Lauri On Wed, Jul 7, 2010 at 6:25 PM, Antoine Toulme <[email protected]>wrote: > Sure. > Actually it could be much better from what I read. You can probably rework > it. > > 1. Buildr::Jetty::REQUIRES is an array, so you can manipulate it: > > At the top of the Buildfile: > > Buildr::Jetty::REQUIRES.clear > Buildr::Jetty::REQUIRES |= [ "org.mortbay.jetty:jetty:jar:#{VERSION}", > "org.mortbay.jetty:jetty-util:jar:#{VERSION}", > "org.mortbay.jetty:servlet-api-2.5:jar:#{VERSION}", > "org.slf4j:slf4j-api:jar:#{SLF4J_VERSION}", > "org.slf4j:slf4j-simple:jar:#{SLF4J_VERSION}", > "org.slf4j:jcl104-over-slf4j:jar:#{SLF4J_VERSION}" ] > > 2. You can set system properties in Buildr very easily: > > Java.java.lang.System.setProperty("foo", "bar") > > Note that this was broken with 1.4. 1.4.1 fixes it. > > On Wed, Jul 7, 2010 at 04:18, Lauri Fjällström > <[email protected]>wrote: > > > Hi, > > > > Buildr seems to be a very nice build tool. However, I'm still having a > > couple of issues with it. So, is there a way in Buildr to change the > Jetty > > version? Also, Can I somehow set some system properties for the Jetty > jvm? > > > > Best, > > Lauri > > >
