You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Michael Dodge (JIRA)" <ji...@apache.org> on 2017/10/30 17:44:01 UTC
[jira] [Resolved] (GEODE-1525) geode-examples rely on GEODE_HOME
env variable
[ https://issues.apache.org/jira/browse/GEODE-1525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Dodge resolved GEODE-1525.
----------------------------------
Resolution: Fixed
This was resolved by other work on geode-examples that removed the `setEnv.sh` scripts entirely.
> geode-examples rely on GEODE_HOME env variable
> ----------------------------------------------
>
> Key: GEODE-1525
> URL: https://issues.apache.org/jira/browse/GEODE-1525
> Project: Geode
> Issue Type: Bug
> Components: docs
> Reporter: Karen Smoler Miller
> Assignee: Karen Smoler Miller
> Labels: bug-hunt
>
> Work currently on the feature/GEODE-33 branch.
> The script {{setEnv.sh}} in the first example (Replicated Region) relies on the user setting the environment variable, {{GEODE_HOME}}, in order to invoke gfsh. This is fine, and the script would fail, telling the user to set the variable. So, things work.
> However, it is likely that many examples will want this same env variable set. Therefore, the top level {{README.md}} should contain a step, perhaps directly after the link to the installation instructions that directs a user to set a {{GEODE_HOME}} environment variable.
> Then, as more examples are added, they can copy the Replicated Region's {{setEnv.sh}} script and also use it.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)