Re: Jdbc connection pooling and PG 7.4 consistently fails

Guys

As a user of your software I'm not too concerned about where the jars are
located, what I do need is clear documentation. This is the one area in
which Postgresql could do with improvement. Ideally I'd like to see this on
the web site and duplicated in the rpm files. Really basic things such as
where files are located and which jar file to use in order to achieve
certain goals. With this information anybody who is capable of installing
Postgresql should be capable of modifying the classpath as well.

regards

Lewis

> -----Original Message-----
> From: Kris Jurka [mailto:books(at)ejurka(dot)com]
> Sent: 19 December 2003 22:10
> To: Lamar Owen
> Cc: Lewis Foti; pgsql-bugs(at)postgresql(dot)org; pgsql-jdbc(at)postgresql(dot)org
> Subject: Re: [BUGS] Jdbc connection pooling and PG 7.4 consistently
> fails
>
>
>
>
> On Fri, 19 Dec 2003, Lamar Owen wrote:
>
> >
> > While I've got your attention on this, where is a good place
> for the RPM to
> > place the jars that would be usable by the largest number of people?
> > Currently they are just plunked down and no real installation
> is being done.
> >
> > Or, to put it a different way, how would you want to see the
> RPM handle the
> > jars? There are significant issues to deal with, but give me
> your wish list.
>
> I'm the wrong person to ask about RPMs a debian fan, but I don't think you
> can do much better than just putting them somewhere. There are four
> different jar files each for a different java runtime environment, so
> you'd need to somehow figure out which version they want. Even if you
> figured out which version they were using, deciding where to put it is
> another difficulty. Classloading in java can be a real rats nest. Just
> putting it in a standard location (Debian uses /usr/share/java for all
> jars) is fine so other people/packages can adjust their classpath to use
> it or symlink it to another location.
>
> Kris Jurka
>
>
>