Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jts-dev] code sprint results for its project

There is no issue with jts-io.jar under java 9, my sentence described us testing the limits of the "automatic module" approach to have a jar that was could be compiled in Java 8 and work with Java 9 applications. We should keep these limitations in mind for further development.

One thing we did notice was that the jts-io-common may as well be renamed jts-io-geojson (since it only has the one format in it).

--
Jody Garnett

On 30 March 2018 at 15:51, Martin Davis <mtnclimb@xxxxxxxxx> wrote:
So is there an issue with using jts-io.jar under Java 9?  And if so, anything we can do to fix it?

On Tue, Mar 27, 2018 at 11:31 AM, Jody Garnett <jody.garnett@xxxxxxxxx> wrote:

One thing we experimented with was confirming that this approach (adding a manifest entry which is ignored by Java 8, but respected by Java 9 "jigsaw") does correctly lock down each JTS jar as a module: The root its-core module publishes a classes into org.locationtech.jts.io - for KML and GML output. When we tried to add a org.locationtech.jts.ioJTSIOVersion class into jts-io-common it failed to load ... because two jars cannot publish into the same package.




_______________________________________________
jts-dev mailing list
jts-dev@xxxxxxxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.locationtech.org/mailman/listinfo/jts-dev



Back to the top