Re: jar naming consitency

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Kris Jurka <books(at)ejurka(dot)com>
Cc: Manuel Sugawara <masm(at)fciencias(dot)unam(dot)mx>, pgsql-jdbc(at)postgresql(dot)org
Subject: Re: jar naming consitency
Date: 2005-02-04 19:01:25
Message-ID: 200502042001.26138.peter_e@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

Am Freitag, 4. Februar 2005 19:22 schrieb Kris Jurka:
> This change was intentional to try and indicate that it is build 310 of
> the 8.0 driver series, not something to do with the postgresql minor
> version 310.

But that would then imply that both releases are the same source, just
different "builds", i.e., compiled on different occasions from the same
source. That is not true. If you release an altered source code, then it
should get a new version.

> Additionally for build 310 the source package name was
> changed postgresql-8.0.309.src.tar.gz to
> postgresql-jdbc-8.0-310.src.tar.gz to try and differentiate it from the
> server as well. We think we've finally hit upon a reasonable convention
> and do intend to stick with it.

I think it would be preferrable if "jdbc" appeared somewhere in the name.
There may be other contexts in which a jar appears in relation with
postgresql.

--
Peter Eisentraut
http://developer.postgresql.org/~petere/

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Oliver Jowett 2005-02-04 19:35:41 Re: BUG #1459: Connection hangs when other connection is not
Previous Message Kris Jurka 2005-02-04 18:22:29 Re: jar naming consitency