You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@geode.apache.org by "Jinmei Liao (JIRA)" <ji...@apache.org> on 2016/01/20 19:44:40 UTC

[jira] [Assigned] (GEODE-749) Improve detection of *.war files

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

Jinmei Liao reassigned GEODE-749:
---------------------------------

    Assignee: Jinmei Liao

> Improve detection of *.war files
> --------------------------------
>
>                 Key: GEODE-749
>                 URL: https://issues.apache.org/jira/browse/GEODE-749
>             Project: Geode
>          Issue Type: Improvement
>          Components: management
>            Reporter: Jens Deppe
>            Assignee: Jinmei Liao
>
> Currently we require a GEMFIRE environment variable to be set in order to detect the location of the pulse.war (and newly) the gemfire.war file.
> I believe this requirement could be avoided by looking for the relevant war file as a resource on the classpath.
> If a user is building a self-contained (possibly executable) application jar, containing all the relevant gemfire jars, they would still need to provide an external pulse.war file as well as set the env variable during execution. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)