Re: Versioning policy PgJDBC - discussion

From: Jorge Solórzano <jorsol(at)gmail(dot)com>
To: Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com>
Cc: Dave Cramer <pg(at)fastcrypt(dot)com>, Gavin Flower <GavinFlower(at)archidevsys(dot)co(dot)nz>, List <pgsql-jdbc(at)postgresql(dot)org>
Subject: Re: Versioning policy PgJDBC - discussion
Date: 2016-11-29 23:54:41
Message-ID: CA+cVU8MWeV8P1_47ORiB7_q94i6P=huOaatvQr0DYpD8XT6Avg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

Or better yet, simply append .jre8 to the version, that way 42.0.0.jre8 >
42.0.0.jre7 > 42.0.0.jre6 and when Java 9 comes out it will be easy to use
.jre9 and there will be no problem to identify what Java version it target.

El mar., 29 de nov. de 2016 10:57 AM, Jorge Solórzano <jorsol(at)gmail(dot)com>
escribió:

> Vladimir, what do you think about using classifier in pgjdbc? It probably
> can simplify build of different jar and at the same time have proper
> versioning in maven.
>
> In maven rules 42.0.0.jre7 > 42.0.0 (jre8) so this should help with
> correct versioning.
>
>
> http://stackoverflow.com/questions/3092085/building-same-project-in-maven-with-different-artifactid-based-on-jdk-used
>
>
> El lun., 28 de nov. de 2016 3:17 PM, Vladimir Sitnikov <
> sitnikov(dot)vladimir(at)gmail(dot)com> escribió:
>
> I've pushed 42.0.0-SNAPSHOT to the pgjdbc/master.
>
> Vladimir
>
> --
>
> Jorge
>
--

Jorge Solórzano
me.jorsol.com

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Dave Cramer 2016-11-30 01:31:51 Re: Versioning policy PgJDBC - discussion
Previous Message Robert Haas 2016-11-29 20:14:48 Re: Patch: Implement failover on libpq connect level.