>I am no Maven/Gradle expert but I'm using PostgreSQL since version 6 and Eclipse/pgCodeKeeper for development, including on macOS. Thus, packaging postgresql-jdbc for macOS is a "personal itch" ;-)
Nice.
>For 42.2.16, I followed the switch from Maven to Gradle for building. But it seems that, since 42.2.20, the Gradle files are not included in the tarballs anymore. Is that voluntary?
There are several ways to build and package pgjdbc:
a) Build from Git sources. That requires Gradle, and it enables running more tests, so you have better confidence in the resulting artifact
and the purpose is to add convenience for cases like Debian that lack Gradle. The set of tests and features is reduced, however, the driver should still work in most cases.
I guess the same might work for pgjdbc as well: the portfile could reference an artifact from
repo1.maven.org rather than building it every time.
The bonus point would be that the jar would be exactly the same as the official one.
Have you considered option c (==grabbing the binaries from
repo1.maven.org)?
Hello, folks.
I occasionally package postgresql-jdbc for MacPorts since version 42.2.8.
I am no Maven/Gradle expert but I'm using PostgreSQL since version 6 and Eclipse/pgCodeKeeper for development, including on macOS. Thus, packaging postgresql-jdbc for macOS is a "personal itch" ;-)
The last version I packaged was 42.2.19. I'm working on 42.3.0 right now but I ran into some issues and wish for some clarifications... :-q
1. For 42.2.16, I followed the switch from Maven to Gradle for building. But it seems that, since 42.2.20, the Gradle files are not included in the tarballs anymore. Is that voluntary?
2. I successfully reverted back to Maven 3.8.2 to build 42.3.0 but what is the preferred way of building in the future: Maven of Gradle ?
Thanks in advance,
G.