Your message dated Fri, 11 Jan 2008 11:55:32 +0530
with message-id <[EMAIL PROTECTED]>
and subject line Bug#404728: groovy: JAVA_HOME should be set according to 
/usr/bin/java
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: groovy
Version: 0.1.0beta10-3
Severity: wishlist

Hello
When starting groovy for the first time it does not seem to be able to
detect my Java environment although I've set that up correctly using
Debian packages. 
As a user already chooses between his default java environments using
update-alternative that decision should be enough for groovy, too,
unless JAVA_HOME has been manuall overridden, of course.

A possible way to detect the java environment would therefore be the
following patch (here only for groovy, should be done for groovyc etc, too):

--- /usr/bin/groovy     2005-10-18 12:39:04.000000000 +0200
+++ /tmp/groovy 2006-12-27 22:28:24.000000000 +0100
@@ -59,6 +59,11 @@
                [ -z "$JAVA_HOME" -a -d 
"/System/Library/Frameworks/JavaVM.framework/Home" ] &&
                        export 
JAVA_HOME="/System/Library/Frameworks/JavaVM.framework/Home"
 
+       else
+         tmp_java_name="$(readlink -f `which java`)"
+         case $tmp_java_name in
+           /usr/lib/jvm/*/bin/java) export 
JAVA_HOME=${tmp_java_name//\/bin\/java/};;
+         esac
        fi
 
 fi

bye,

-christian-

-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-3-686
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) (ignored: 
LC_ALL set to [EMAIL PROTECTED])

Versions of packages groovy depends on:
ii  ant               1.6.5-6                Java based build tool like make
ii  ant-optional      1.6.5-6                Java based build tool like make - 
ii  junit             3.8.1.1-7              Automated testing framework for Ja
ii  libasm-java       1.5.3-4                Java bytecode manipulation framewo
ii  libbsf-java       1:2.3.0+cvs20050308a-1 Bean Scripting Framework to suppor
ii  libclassworlds-ja 1.0.1-1.1              Java ClassLoader Framework
ii  libcommons-cli-ja 1.0-8                  API for working with the command l
ii  libcommons-collec 3.1a-3.1               A set of abstract data type interf
ii  libcommons-loggin 1.0.4-5                commmon wrapper interface for seve
ii  libmockobjects-ja 0.09-1.1               Framework for developing and using
ii  libmx4j-java      2.1.1-4                An open source implementation of t
ii  libregexp-java    1.4-3                  regular expression library for Jav
ii  libservlet2.3-jav 4.0-8                  Servlet 2.3 and JSP 1.2 Java class
ii  sun-java5-jre [ja 1.5.0-10-1             Sun Java(TM) Runtime Environment (

groovy recommends no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
Version: 1.5.0-1
Source: groovy

On Tue, 18 Dec, 2007 at 02:38:45PM +0530, Varun Hiremath wrote:
> Hi Christian,
> 
> On Wed, 27 Dec, 2006 at 10:30:14PM +0100, Christian Hammers wrote:
> > Package: groovy
> > Version: 0.1.0beta10-3
> > Severity: wishlist
> > 
> > Hello
> > When starting groovy for the first time it does not seem to be able to
> > detect my Java environment although I've set that up correctly using
> > Debian packages. 
> > As a user already chooses between his default java environments using
> > update-alternative that decision should be enough for groovy, too,
> > unless JAVA_HOME has been manuall overridden, of course.
> > 
> 
> We have recently updated groovy to the latest upstream version 1.5,
> and I think the JAVA_HOME is set properly in the new version. Could
> you please check if the new version of groovy loads properly and let
> us know if this bug could be closed?

I am closing this bug as it has been fixed in the 1.5 version of
groovy.

Thanks
Varun

-- 
Varun Hiremath
Undergraduate Student,
Aerospace Engineering Department,
Indian Institute of Technology Madras,
Chennai, India
-------------------------------------
Homepage : http://varun.travisbsd.org


--- End Message ---
_______________________________________________
pkg-java-maintainers mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers

Reply via email to