Yes, you do need to support asenv.conf/bat as well - zip bundles will
obviously depend on JAVA_HOME value from the environment, but installer
bundles will set AS_JAVA location in asenv.conf during installation and
user is always allowed to add this entry to asenv.conf file and expect
it to be picked up as runtime for any script.
FWIW, Kedar modified asadmin to use this approach for Preview release so
you can use JDK location handling from asadmin as template for all other
scripts.
Thanks,
Snjezana
Marina Vatkina wrote:
> Do we now only support JAVA_HOME set in the local environment or
> v2-way of using asenv.conf is/will be supported as well?
>
> I'm porting rmic execution code from v2, and wondering how much of the
> old code do I need to keep.
>
> thanks,
> -marina
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>