Re: Pre-processing during build

From: Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com>
To: Dave Cramer <pg(at)fastcrypt(dot)com>
Cc: John R Pierce <pierce(at)hogranch(dot)com>, List <pgsql-jdbc(at)postgresql(dot)org>
Subject: Re: Pre-processing during build
Date: 2015-06-18 19:33:07
Message-ID: CAB=Je-HLNXO3=p0JNoG9nkE-HDmYycWqeZT-dK69nkm-3tW1_A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

John> and that stuff NEVER gets updated until the equipment is replaced.

That is cool. However, that means you don't care if pgjdbc drops
updates for JDK6, do you?

My theory is as follows: if there is a nice "decay of download rate",
then we might have a bit more educated guess on "the number of
supported JDKs"

Dave> I provide professional services to companies that do

Ok, let's try supporting JDK6.

So, the next step is to start from
https://github.com/pgjdbc/pgjdbc/pull/322 and try to split it into
several maven submodules.

The interesting question is if we want to those submodules (jdbc4,
jdbc41, jdbc42) to be public (in other words, allow users depend on
them) or if we consider them a pure implementation detail.
In the latter case, we might want to have some fixed name of the
module that includes the latest driver.

I would prefer to have a single artifact in the "public API" that
includes all the jdbc versions.

Vladimir

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Markus KARG 2015-06-18 19:44:28 Re: Pre-processing during build
Previous Message Dave Cramer 2015-06-18 19:25:53 Re: Pre-processing during build