GitHub user markito opened a pull request:

    https://github.com/apache/incubator-geode/pull/171

    feature/geode 33

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/apache/incubator-geode feature/GEODE-33

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-geode/pull/171.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #171
    
----
commit 4b6200d0ffc92c1e9fe9b1695c0f5ccd99e6c387
Author: William Markito <wmark...@pivotal.io>
Date:   2016-06-09T03:30:32Z

    [GEODE-33] - Adding geode-example module
    Creating a simple example for replicated regions to test the proposed 
example model
    Adding script tests
    Adding server folders to gitignore
    Adding gitignore and readme files

commit d2ec280df6d3feacccdb5dba4a114ef086a71717
Author: Karen Miller <kmil...@pivotal.io>
Date:   2016-06-15T21:34:37Z

    GEODE-1531: Improve README.md for replicated example
    
    - Improved the appearance of the markdown
    
    - Added commands for how to kill a single server
    
    - Added last step to run scripts/stopAll.sh so the system is
      shut down when the example ends, not leaving a locator and
      a server running
    
    - Improved the prose describing what the example does

commit 21d30ab92d2a2146207186a690eb5a36d42e7059
Author: Karen Miller <kmil...@pivotal.io>
Date:   2016-06-15T22:30:03Z

    GEODE-1525: Examples README.md should set env variable
    GEODE-1523: Improve examples README.md markdown
    
    This PR fixes addresses both GEODE-1525 and GEODE-1523, as they
    both change the contents of the same file: geode-examples/README.md.
    
    - Each example will likely use a scripts/setEnv.sh script to set
      the path to gfsh. The script depends on a GEODE_HOME environment
      variable, so this top level of instructions for setting up
      the examples now tells the user to set a GEODE_HOME env variable
      directly after the installation.
    
    - Implement a more strict markdown that displays correctly for a
      wide variety of markdown implementations.
    
    - Put in links for the 3 references.
    
    - Improve the prose.

commit e24a47110fb504cf4b2980305ab492e23d70a361
Author: Karen Miller <kmil...@pivotal.io>
Date:   2016-06-15T18:07:03Z

    Merge #158 into feature/GEODE-33
    GEODE-1530: geode-examples setEnv.sh script needs to export path
    
    Without an export of the path, using the GEODE_HOME env variable,
    the scripts/startAll.sh script will pick up the first gfsh in the
    path that it finds.
    
    Also updated the scripts/stopAll.sh script to run the setEnv.sh
    script, so that stopAll.sh uses the correct gfsh.

commit f371995ebc0ed075342a1ae41ed8dde8189c97c3
Author: William Markito <wmark...@pivotal.io>
Date:   2016-06-20T15:56:07Z

    Merge #159 into feature/GEODE-33

commit d67bf627c096e025cb0f7db7af49a6cfbc30bc06
Author: William Markito <wmark...@pivotal.io>
Date:   2016-06-20T15:57:16Z

    Merge #160 into feature/GEODE-33

commit a31b8482a3306856f9e97459649ac38d0db709bf
Author: William Markito <wmark...@pivotal.io>
Date:   2016-06-21T07:00:41Z

    [GEODE-33] Fixed hardcoded path for resources on tests
    - Included rat exclusion rules

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to