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] Closed: (GERONIMO-4093) gsh scripts are not using setjavaenv or optional setenv script
Date Thu, 25 Sep 2008 16:59:44 GMT

     [ https://issues.apache.org/jira/browse/GERONIMO-4093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Donald Woods closed GERONIMO-4093.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 2.1.4

Updates made in GERONIMO-4312 should resolve your concerns on requiring JAVA_HOME.
The optional setenv script can still be useful for our users, by allowing them to provide
env vars for such cases as running Geronimo as a service on Linux/Unix.
The provided setjavaenv script is still useful, as it validates that a Java runtime can be
found.


> gsh scripts are not using setjavaenv or optional setenv 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.4, 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