GEOWAVE-415: update to geotools 14.1#590
Merged
dcy2003 merged 2 commits into0.9.0-RC1-mergefrom Jan 27, 2016
Merged
Conversation
b9f0117 to
d196f01
Compare
Contributor
There was a problem hiding this comment.
Should probably either rip this commented code out entirely, OR put a FIXME in here with some notes about why it's commented out so we remember why/when to put it back eventually...
Contributor
Author
There was a problem hiding this comment.
good point, let's rip it out...tests are passing and we have revision history to go back to if for some reason we run into a snag later on
dcy2003
added a commit
that referenced
this pull request
Jan 27, 2016
GEOWAVE-415: update to geotools 14.1
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
geotools 14.2 is out but geoserver 2.8.2 is not, so I stuck with this release for now, the updates to new minor releases typically don't involve api changes anyways.