Hi guys, I'd like to open a new discussion with Buildr and offer a new insight on Buildr's link to Java.
>From day one, Buildr was tightly bound to Java. We use either RJB or JRuby as the gateway to Java, and we have one common API to discuss with it. We use the Java integration in critical yet well defined operations: compiling is for sure one, we also run some tools directly. I think we could find a way to make Buildr less resilient on Java. I wrote an experimental compiler that relies on an external javac recently here: http://github.com/intalio/buildr4osgi/blob/master/lib/buildr4osgi/compile/external.rb This compiler helps me as I need to use a different JDK for part of the projects I have to compile. I think the Java integration of Buildr helps starting the JVM only once - I also think we could support most scenarios by calling Java over a subshell. I don't know how much more expensive it would turn out to be but I see it as a good option - when RJB breaks, or when JFFI refuses to load, which happens all too often. We know the main problem of Buildr is its installation story. How about we give a drop and run Buildr gem that just relies on the JVM by calling it, instead of linking to it ? That would make for less headaches and work allright on most OSes. I would like to make such an implementation - as time permits. Please let me know what you think. Thanks, Antoine
