[FOLIO-2314] Release fork of vertx-mysql-postgresql-client Created: 21/Oct/19  Updated: 03/Jun/20  Resolved: 23/Oct/19

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Task Priority: P2
Reporter: Ian Hardy Assignee: Ian Hardy
Resolution: Done Votes: 0
Labels: devops, platform-backlog
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Blocks
blocks RMB-485 RMB modules leak PostgreSQLConnection... Closed
Relates
relates to RMB-485 RMB modules leak PostgreSQLConnection... Closed
Sprint: CP: sprint 75
Story Points: 0.5
Development Team: Core: Platform

 Description   

Release these two new release branches of our fork https://github.com/folio-org/vertx-mysql-postgresql-client :

  • release-connection-pool-3-8-2-folio-1
  • release-connection-pool-3-8-2-folio-2

Will need a simple Jenkinsfile to make future releases from this fork routine.

Note that vert.x split the vertx-mysql-postgresql-client into two clients (see https://github.com/vert-x3/vertx-mysql-postgresql-client/blob/3.8/README.adoc ):

  • (Soon to be legacy) Scala based version
  • (Soon to be may mainline) Kotlin/jasync based version

The connection release patch is in the Kotlin/jasync based version only. Change

<dependency>
   <groupId>io.vertx</groupId>
   <artifactId>vertx-mysql-postgresql-client</artifactId>
   <version>3.5.1-FOLIO.1</version><!--$NO-MVN-MAN-VER$-->
 </dependency>

to

<dependency>
  <groupId>io.vertx</groupId>
  <artifactId>vertx-mysql-postgresql-client-jasync</artifactId>
  <version>3.8.2-FOLIO-2</version><!--$NO-MVN-MAN-VER$-->
</dependency>

by altering both artifactId (add -jasync) and version,



 Comments   
Comment by Ian Hardy [ 22/Oct/19 ]

Hongwei Ji Did a mvn deploy from the two branched Julian requested (should be able to see them under https://repository.folio.org/#browse/browse:maven-releases in the io directory).

Comment by Hongwei Ji [ 22/Oct/19 ]

Thanks Ian Hardy.

Generated at Thu Feb 08 23:19:46 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.