Re: [pgjdbc] Implement JDBC specs via pre-processor step (#435)

From: Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com>
To: Álvaro Hernández Tortosa <aht(at)8kdata(dot)com>
Cc: Pavel Kajaba <pkajaba(at)redhat(dot)com>, Stephen Nelson <stephen(at)eccostudio(dot)com>, List <pgsql-jdbc(at)postgresql(dot)org>, Pavel Raiskup <praiskup(at)redhat(dot)com>, Dave Cramer <pg(at)fastcrypt(dot)com>
Subject: Re: [pgjdbc] Implement JDBC specs via pre-processor step (#435)
Date: 2016-01-22 07:42:49
Message-ID: CAB=Je-GEA9vuxUqZNd6anG=C_6HP4M_iN6Xt-Ha8CrPkXbfrLA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

Álvaro>Run "mvn dependency:list"

mvn dependency:analyze-report allows to capture "Used but undeclared
dependencies" and "Unused but declared dependencies" as well.

Álvaro>- xml-resolver: pretty old code

I've no idea what it is doing there. It is marked as compile-time
dependency, however the code compiles without it just fine.
I think it can be just dropped.

Álvaro> OK, so here's how to reproducible check the dependencies of
the maven project:

What we miss is:
1) Fedora-like CI environment. It makes little sense optimizing
pgjdbc's dependencies if those dependencies are already present in
Fedora-like build boxes.
Is there a CI for Fedora builds?
How do we validate that "the specific changes to pgjdbc" indeed help
Fedora packaging?

2) Requirements. I'm sure the first dozen of builds will fail due to
packaging limitations. It is much better to know the limitations
beforehand than running into them at Fedora CI builds.

Vladimir

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Pavel Raiskup 2016-01-22 08:36:29 Re: [pgjdbc] Implement JDBC specs via pre-processor step (#435)
Previous Message Vitalii Tymchyshyn 2016-01-22 00:39:17 Re: Step towards being able to build on Linux (Pull request #435)