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
In 2014 I manually added a relocation artifact from org.firebirdsql.jdbc:jaybird:2.2.5 to org.firebirdsql.jdbc:jaybird-jdk17 in the hope that this would be a sufficient prompt for people to move to the new version specific artifacts. Unfortunately, this doesn't work well enough.
I have now added relocation artifacts from org.firebirdsql.jdbc:jaybird:2.2.14 to org.firebirdsql.jdbc:jaybird-jdk17 and org.firebirdsql.jdbc:jaybird:3.0.5 to org.firebirdsql.jdbc:jaybird-jdk18. From now on these should be deployed with each release. To this end, the proper relocation artifacts should be generated as part of the build (but only for the relevant Java version, so for 2.2.x for Java 7, and for 3.0.x and 4.0.x for Java 8) so I can easily deploy them to Maven.
description: In 2014 I manually added a relocation artifact from org.firebirdsql.jdbc:jaybird:2.2.5 to org.firebirdsql.jdbc:jaybird-jdk17 in the hope that this would be a sufficient prompt for people to move the the new version specific artifacts. Unfortunately, this doesn't work well enough.
I have now added relocation artifacts from org.firebirdsql.jdbc:jaybird:2.2.14 to org.firebirdsql.jdbc:jaybird-jdk17 and org.firebirdsql.jdbc:jaybird:3.0.5 to org.firebirdsql.jdbc:jaybird-jdk18. From now on these should be deployed with each release. To this end, the proper relocation artifacts should be generated as part of the build (but only for the relevant Java version, so for 2.2.x for Java 7, and for 3.0.x and 4.0.x for Java 8) so I can easily deploy them to Maven.
=>
In 2014 I manually added a relocation artifact from org.firebirdsql.jdbc:jaybird:2.2.5 to org.firebirdsql.jdbc:jaybird-jdk17 in the hope that this would be a sufficient prompt for people to move to the new version specific artifacts. Unfortunately, this doesn't work well enough.
I have now added relocation artifacts from org.firebirdsql.jdbc:jaybird:2.2.14 to org.firebirdsql.jdbc:jaybird-jdk17 and org.firebirdsql.jdbc:jaybird:3.0.5 to org.firebirdsql.jdbc:jaybird-jdk18. From now on these should be deployed with each release. To this end, the proper relocation artifacts should be generated as part of the build (but only for the relevant Java version, so for 2.2.x for Java 7, and for 3.0.x and 4.0.x for Java 8) so I can easily deploy them to Maven.
Submitted by: @mrotteveel
In 2014 I manually added a relocation artifact from org.firebirdsql.jdbc:jaybird:2.2.5 to org.firebirdsql.jdbc:jaybird-jdk17 in the hope that this would be a sufficient prompt for people to move to the new version specific artifacts. Unfortunately, this doesn't work well enough.
I have now added relocation artifacts from org.firebirdsql.jdbc:jaybird:2.2.14 to org.firebirdsql.jdbc:jaybird-jdk17 and org.firebirdsql.jdbc:jaybird:3.0.5 to org.firebirdsql.jdbc:jaybird-jdk18. From now on these should be deployed with each release. To this end, the proper relocation artifacts should be generated as part of the build (but only for the relevant Java version, so for 2.2.x for Java 7, and for 3.0.x and 4.0.x for Java 8) so I can easily deploy them to Maven.
Commits: 0330d07 d81dc0c 8457550
The text was updated successfully, but these errors were encountered: