geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Donald Woods (JIRA)" <j...@apache.org>
Subject [jira] Commented: (GERONIMO-4093) gsh scripts are not looking for optional setjavaenv script
Date Tue, 03 Jun 2008 12:58:44 GMT

    [ https://issues.apache.org/jira/browse/GERONIMO-4093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12601913#action_12601913
] 

Donald Woods commented on GERONIMO-4093:
----------------------------------------

Well, gsh only looks for JAVA_HOME, whereas deploy/geronimo can use either JRE_HOME or JAVA_HOME
and actually prefers JRE_HOME unless you are starting the server in debug mode, so we've lost
that option with gsh.
Also, the setenv/setjavaenv scripts allowed users to override settings, without mucking with
server provided files.


> gsh scripts are not looking for optional setjavaenv script
> ----------------------------------------------------------
>
>                 Key: GERONIMO-4093
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-4093
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>    Affects Versions: 2.1, 2.1.1, 2.1.2, 2.2
>            Reporter: Donald Woods
>            Assignee: Donald Woods
>             Fix For: 2.1.2, 2.2
>
>
> gsh scripts are not allowing users to provide the optional setjavaenv scripts, like the
previous geronimo/deploy scripts allowed.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message