Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade GeoTools 22.x #361

Merged
merged 17 commits into from Jan 1, 2020
Merged

Upgrade GeoTools 22.x #361

merged 17 commits into from Jan 1, 2020

Conversation

fgdrf
Copy link
Contributor

@fgdrf fgdrf commented Oct 20, 2019

In behalf of @egouge I created this pull-request for master

egouge and others added 13 commits September 27, 2019 16:28
Signed-off-by: egouge <egouge@refractions.net>
execution

Signed-off-by: Nikolaos Pringouris <nprigour@gmail.com>
further modification required for successful compilation & test execution
Signed-off-by: egouge <egouge@refractions.net>
…pport CacheInterceptor

Signed-off-by: egouge <egouge@refractions.net>
…pport CacheInterceptor

Signed-off-by: egouge <egouge@refractions.net>
Signed-off-by: Nikolaos Pringouris <nprigour@gmail.com>
addition of org.apache.commons.codec in base-feature plugins
Signed-off-by: Nikolaos Pringouris <nprigour@gmail.com>
Signed-off-by: egouge <egouge@refractions.net>
Signed-off-by: Frank Gasdorf <fgdrf@users.sourceforge.net>
@nprigour
Copy link
Contributor

nprigour commented Dec 3, 2019

Hi,

May be it is worth to move to recently released geotools 22.1 (instead of 22.0) which is supposed to be more mature.
During this upgrade we should consider:

@fgdrf
Copy link
Contributor Author

fgdrf commented Dec 3, 2019

Actually @jodygarnett wrote something in GeoTools mailing list, that 22.1 is not "valid". I guess we should move on to 22.2 once it is avalable.

The prior 22.1 build was one of those that failed over JDK issues so we only have partially

I'm not really sure about the statement, itf its a good idea to upgrade to 22.2 anyway:

I accidentally made a 22.2 release, see user list for discussion about renaming those folders to 22.2-mistake to avoid causing problems downstream

@jodygarnett can you give us any advice how to proceed with 22.x series?

@jodygarnett
Copy link
Contributor

ha ha, I screwed up so bad and different development teams around the world are all confused :P

The https://sourceforge.net/projects/geotools/files/GeoTools%2022%20Releases/22.1/ release is the latest.

I just typed the wrong version number into the release script :P

Copy link
Contributor Author

@fgdrf fgdrf left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ha ha, I screwed up so bad and different development teams around the world are all confused :P

The https://sourceforge.net/projects/geotools/files/GeoTools%2022%20Releases/22.1/ release is the latest.

I just typed the wrong version number into the release script :P

Can happen :) However, are you saying that 22.1 is fine?

@jodygarnett
Copy link
Contributor

jodygarnett commented Dec 3, 2019

I have updated the release announcement to help make this clear: https://geotoolsnews.blogspot.com/2019/11/geotools-221-released.html

Update: Jody would like to apologize for accidentally releasing "22.2" while testing out JDK versions above. The maven repository folders have been renamed "22.2-mistake" to avoid causing problems. GeoTools 22.2 is scheduled for January.

Sorry for the trouble.

@fgdrf
Copy link
Contributor Author

fgdrf commented Dec 3, 2019

Thank you for clarification! IMO my pull for @egouge (see egouge#4) is still valid (which upgrades to 22.1)

@nprigour
Copy link
Contributor

nprigour commented Dec 3, 2019

Ok @fgdrf,
I was not aware of your latest pull to @egouge branch :)

upgrade to latest GeoTools release 22.1
@fgdrf
Copy link
Contributor Author

fgdrf commented Dec 3, 2019 via email

@fgdrf fgdrf added this to the 2.2.0 milestone Dec 28, 2019
fgdrf and others added 3 commits January 1, 2020 20:22
* resolves gt-22.1 compile issues
* fixes test case

Signed-off-by: Frank Gasdorf <fgdrf@users.sourceforge.net>
Resolved Merge conflicts with latest from master
@fgdrf
Copy link
Contributor Author

fgdrf commented Jan 1, 2020

Cool, all active tests passed :D (see travis build)

@fgdrf fgdrf merged commit 9d2a8d6 into locationtech:master Jan 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants