On Jun 26, 2008, at 8:48 AM, Russel Winder wrote:
On Thu, 2008-06-26 at 08:00 +0200, Hans Dockter wrote:
time buildr build test=off (based on CRuby. I had no time yet to
install the newest JRuby. I think the JRuby based performance is more
relevant. As otherwise you can't use any Java libraries with your
build logic).
I think this is false logic. If Buildr on CRuby is faster than Buildr
on JRuby then Buildr on CRuby should be the version used for
benchmarking Gradle -- well actuall always use both. People will not
care whether they can call Java library functions in their build, they
will only care how fast the build is.
I have no problem in benchmarking both (as I have done in my email).
But a complex build with many projects is were this performance
matters most. And in such builds it is likely to have complex custom
build logic. And at least Java developers would like to use Java
libraries for implementing thus logic. Therefore I think for one,
that a Java build tool should be able to run on the JVM. And I think
that this is the most relevant platform. It is at least important to
point out the limitations to Java users if the C based buildr version
is used.
- Hans
--
Russel.
====================================================
Dr Russel Winder Partner
Concertant LLP t: +44 20 7585 2200, +44 20 7193 9203
41 Buckmaster Road, f: +44 8700 516 084
London SW11 1EN, UK. m: +44 7770 465 077
--
Hans Dockter
Gradle Project lead
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
