updates for geowave 0.9.3 release #1933
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rfecher
force-pushed
the
feature/rfecher/geowave-0.9.3
branch
3 times, most recently
from
66e2e6c
to
91c252a
Compare
Signed-off-by: Rich Fecher <rfecher@gmail.com>
rfecher
force-pushed
the
feature/rfecher/geowave-0.9.3
branch
from
91c252a
to
adb4b70
Compare
|
Awesome, thanks! |
lossyrob
approved these changes
Dec 21, 2016
This was referenced Dec 22, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
pretty basic version updates to the 0.9.3 release, with a small code change to a simplification on the API
most significant impact is going to be upgrading to geotools 16.0 from 14.4 but it the project does build on 16.0