Issue Details (XML | Word | Printable)

Key: JDBC-547
Type: Improvement Improvement
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Mark Rotteveel
Reporter: Mark Rotteveel
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Jaybird JCA/JDBC Driver

Generate dependency relocation artifact for org.firebirdsql.jdbc:jaybird for each release

Created: 10/Sep/18 12:28 PM   Updated: 06/Apr/19 10:59 AM
Component/s: None
Affects Version/s: None
Fix Version/s: Jaybird 2.2.15, Jaybird 3.0.6, Jaybird 4


 Description  « Hide
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.

 All   Comments   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Mark Rotteveel added a comment - 13/Sep/18 03:48 PM
Changed build scripts to generate appropriate pom for relocation.