GitHub user kjduling opened a pull request:
https://github.com/apache/incubator-geode/pull/227
Rename servlet URLs from gemfire to geode
Renamed gemfire-api/v1 to geode/v1
Renamed gemfire/v1 to geode-mgmt/v1
Verified old context paths still work, so both can be used for a time.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/kjduling/incubator-geode feature/GEODE-1467
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-geode/pull/227.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 #227
----
commit 96c151ad46f2656b3089db22dbc76e86233fe45a
Author: Kevin J. Duling <[email protected]>
Date: 2016-07-28T22:07:14Z
GEODE-1467: Rename servlet URLs from gemfire to geode
Add a second servlet for each. This allows both the old and new URL
contexts for a time.
Updated some unit tests to use Parameterized so that both endoints will be
tested.
commit 1053b8d384863c488af6906ab266106396e44928
Author: Kevin J. Duling <[email protected]>
Date: 2016-08-01T23:50:12Z
GEODE-1467: Rename servlet URLs from gemfire to geode
Renamed the servlet.xml files back due to precheckin issues
commit 156d178550e44203c17cfb3d7805dbb2cf5fdf49
Author: Kevin J. Duling <[email protected]>
Date: 2016-08-02T15:52:56Z
GEODE-1467: Rename servlet URLs from gemfire to geode
Copied servlet files for new name (will delete old servlet files later)
commit c3f2ccb5cf954e9d0a8899a4a55604f47aeb25a9
Author: Kevin J. Duling <[email protected]>
Date: 2016-08-02T15:53:42Z
Merge branch 'develop' of github.com:apache/incubator-geode into
feature/GEODE-1467
commit cb9d6faf73b75571d8ba1e6e1509947cd4c1ce54
Author: Kevin J. Duling <[email protected]>
Date: 2016-08-02T17:30:09Z
GEODE-1467: Rename servlet URLs from gemfire to geode
Remove old servlets.
----
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
