dev@glassfish.java.net

Are we going to use asenv.conf/bat for v3?

From: Bhakti Mehta <Bhakti.Mehta_at_Sun.COM>
Date: Mon, 22 Sep 2008 14:39:07 -0700

Hi,
In v2 we could modify AS_JAVA in gf/config/asenv.conf and that would
start the server with that jdk and not with what is set in your JAVA_HOME

In v3 I see this value hardcoded in
v3/distributions/nucleus-base/config/asenv.*
set AS_JAVA=c:\java\jdk1.6.0\jre/..
whereas asenv.conf does not have that variable and right now we just
start using the JAVA_HOME set in the env,

Is this the way we are going to continue for v3?

The reason I am asking is I got this bug
https://glassfish.dev.java.net/issues/show_bug.cgi?id=6193 where
tools.jar needs to be added to the metro scripts

Do I just set it from the environment variable or is there some
requirement to use from asenv.con/bat (which if is the case I think is
broken right now)
Regards,
Bhakti