|
If you were logged in you would be able to see more operations.
|
|
|
|
With the new release schedule for Java, we'll 'soon' reach Java 15, which means the current Maven artifact naming scheme of jaybird-jdkxx becomes ambiguous (as jaybird-jdk15 is Java 5, etc).
Possible schemes:
1) Use jaybird-javaXX -> jaybird-java11, etc for new versions; continue using jaybird-jdk17 and jaybird-jdk18 for Java 7 and 8
2) Switch back to jaybird for Java 11+ versions; continue using jaybird-jdk17 and jaybird-jdk18 for Java 7 and 8
Something else?
Use multi-release jars?
|
|
Description
|
With the new release schedule for Java, we'll 'soon' reach Java 15, which means the current Maven artifact naming scheme of jaybird-jdkxx becomes ambiguous (as jaybird-jdk15 is Java 5, etc).
Possible schemes:
1) Use jaybird-javaXX -> jaybird-java11, etc for new versions; continue using jaybird-jdk17 and jaybird-jdk18 for Java 7 and 8
2) Switch back to jaybird for Java 11+ versions; continue using jaybird-jdk17 and jaybird-jdk18 for Java 7 and 8
Something else?
Use multi-release jars? |
Show » |
|
Task
Closed
Major
Devise new Maven naming scheme for Java 9+ versions