You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the upgrade to GeoAPI 3.0.2 (issue #64), PROJ-JNI is now a Jigsaw module (issue #15). We have done that while preserving Java 8 compatibility by using the multi-version capability of JAR files. However it makes the project more complicated. A few source files are duplicated in the java9 directory with slightly different code, for example with slightly different use of ServiceLoader. Those duplications increase the risk of discrepancies if a developer changes a Java 8 source file and forget to update the corresponding Java 9+ source file. The root pom.xml file is also more complicated with an Ant task for generating the multi-version JAR file.
When can simplify the project by dropping Java 8 support. The question is when? (no need to be now since we have a solution that works for now).
The text was updated successfully, but these errors were encountered:
As discussed in #67, the 2.0 release has a note saying that it may be the last release supporting Java 8. Having hear no comment in the last 2 months, we will proceed unless there is a last minute objection posted on this issue.
With the upgrade to GeoAPI 3.0.2 (issue #64), PROJ-JNI is now a Jigsaw module (issue #15). We have done that while preserving Java 8 compatibility by using the multi-version capability of JAR files. However it makes the project more complicated. A few source files are duplicated in the
java9
directory with slightly different code, for example with slightly different use ofServiceLoader
. Those duplications increase the risk of discrepancies if a developer changes a Java 8 source file and forget to update the corresponding Java 9+ source file. The rootpom.xml
file is also more complicated with an Ant task for generating the multi-version JAR file.When can simplify the project by dropping Java 8 support. The question is when? (no need to be now since we have a solution that works for now).
The text was updated successfully, but these errors were encountered: