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

Devise new Maven naming scheme for Java 9+ versions [JDBC563] #596

Closed
firebird-automations opened this issue Nov 4, 2018 · 4 comments
Closed

Comments

@firebird-automations
Copy link

Submitted by: @mrotteveel

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?

@firebird-automations
Copy link
Author

Modified by: @mrotteveel

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?

=>

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?

@firebird-automations
Copy link
Author

@firebird-automations
Copy link
Author

Modified by: @mrotteveel

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

@firebird-automations
Copy link
Author

Modified by: @mrotteveel

status: Resolved [ 5 ] => Closed [ 6 ]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants