startGroovy tries to locate javac in order to build the JAVA_HOME
variable. We should not depend on the JDK, groovy works very well on a
small JRE, but startGroovy should be patched to use the default location
of JAVA_HOME on a Debian system.
Ludovic
Le 05/08/2010 03:00, Miguel Landaeta a écrit :
Hi Torsten,
On Wed, Aug 4, 2010 at 8:09 PM, Torsten Werner<twer...@debian.org> wrote:
On Wed, Aug 4, 2010 at 8:40 PM, Miguel Landaeta<mig...@miguel.cc> wrote:
groovy is unusable without a JDK.
is it really unusable without the compiler or is the start just broken?
Well, groovy source code is dynamically compiled to JVM bytecode
so I think a JDK must be present. The startGroovy script tries to
detect where in the system is installed javac.
I didn't noticed this bug before because I always install a JDK.
BTW, the patch don't apply cleanly on what is on svn because there
is an ongoing work to package groovy 1.7.4 but it is stalled because
jansi library it is not in Debian. I think I'm going to file an ITP for that
library.
Cheers,
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
