On Thu, Mar 15, 2018 at 4:56 PM, Jody Garnett
wrote:
> But yeah, if we can keep working on both, that would be great.
>>
>
> It looks like we can, and I would rather do what we can now (units
> library, repackage, spring 5) so we have less panic at java 8 EOL.
>
Agreed, spreading the improvement
>
> Not even the GeoTools/GeoServer ones? :)
>
Ha ha, I was focused on the java roadmap.
>
> But yeah, if we can keep working on both, that would be great.
>
It looks like we can, and I would rather do what we can now (units library,
repackage, spring 5) so we have less panic at java 8 EOL.
>
>
On Thu, Mar 15, 2018 at 4:41 PM, Jody Garnett
wrote:
> I do not know of any March 2019 releases
>
Not even the GeoTools/GeoServer ones? :)
But yeah, if we can keep working on both, that would be great.
Cheers
Andrea
==
GeoServer Professional Services from the experts! Visit http://goo.gl/it4
I should of used more words, we can do the repackage, and add MANIFEST
entries while still staying on Java 8. This next release of GeoTools should
work on both Java 8 and Java LTS 18.9. The goal is to make this GeoTools
jigsaw ready, giving applications like GeoServer plenty of breathing room
to mi
Hi Jody,
forcing the build off Java 8 seems like a problem, at least in the short
term. I'd wait for
such a move until the March 2019 release.
A switch to Java 11 (LTS) by September "might" work, but it's going to be
kind of risky,
the GA for it is also September 2018, so we'd have a new GT releas
Had a chat with Torben, updating
https://github.com/geotools/geotools/wiki/Java-9-Compatibility page into a
sensible list.
There are three activities that are ready to be worked on next:
* Migrate to JSR-363 library
* jigsaw dependency audit
* Java Jigsaw module system repackage
Technically we c
