Re: Merge pgjdbc-parent-poms project into pgjdbc please

On 25 January 2016 at 08:39, Pavel Raiskup <praiskup(at)redhat(dot)com> wrote:

> On Monday 25 of January 2016 13:17:41 Vitalii Tymchyshyn wrote:
> > Well, most of enterprise backend servers run on linux. Most are on
> > commercial, like RedHat or Suse. As of OSGI, it's supported by Fedora
> (with
> > Felix packages), it's just not very up to date. And PostgreSQL uses quite
> > recent features. As I already noted, osgi-enterprise can be replaced with
> > OPS4J package if there are OSSing problems with org.osgi.
>
> ACK here. There are (or were) people which cared about Felix packages.
> This might change, but it should not block redistribution of JDBC. It is
> really natural to have conditional dependencies.
>
> > Also I suppose other projects are somehow patched because they don't
> > usually use felix packages.
>
> What projects do you mean here? Maybe we can learn from them, somehow.
>
> > One more thing: as for me it would be confusing to have not
> > fully-featured driver distributed without being marked somehow.
>
> Right, then we can probably discuss how to Linux specific builds somehow.
> There must be a way?
> Side note: Vitalii, as you sort of trust maven repositories, you are fine
> to use (online) 'maven install', then you'll get a lot of dead code (in
> fully featured build) on Linux, but anyway -- you are fine. Some
> enterprise users however trust Linux distributors and for them can be
> maven repository insecure.
>
> Well like it or not, spring is arguably the largest enterprise java
dependency and it has hundreds if not thousands of dependencies which
enterprise users happily download. So I'm not sure how your argument holds
water. I would imagine from a redhat perspective redhat is the only trusted
source. However this is 2016 and the sheer volume of dependencies modern
software requires makes this presumption untenable.

This argument is not constructive but an attempt to show another point of
view.

I have asked to join the osgi-dev list and will ask them how to deal with
this issue

Dave Cramer

davec(at)postgresintl(dot)com
www.postgresintl.com