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

Generate dependency relocation artifact for org.firebirdsql.jdbc:jaybird for each release [JDBC547] #580

Closed
firebird-automations opened this issue Sep 10, 2018 · 5 comments

Comments

@firebird-automations
Copy link

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

@firebird-automations
Copy link
Author

Modified by: @mrotteveel

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.

@firebird-automations
Copy link
Author

Modified by: @mrotteveel

Fix Version: Jaybird 2.2.15 [ 10860 ]

Fix Version: Jaybird 3.0.6 [ 10883 ]

Fix Version: Jaybird 4 [ 10441 ]

Version: Jaybird 2.2.15 [ 10860 ] =>

Version: Jaybird 3.0.6 [ 10883 ] =>

Version: Jaybird 4 [ 10441 ] =>

@firebird-automations
Copy link
Author

Commented by: @mrotteveel

Changed build scripts to generate appropriate pom for relocation.

@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