Re: Are pgrpm changes for JDBC discussed here before submission? - Mailing list pgsql-jdbc

From John Harvey
Subject Re: Are pgrpm changes for JDBC discussed here before submission?
Date
Msg-id CABcP5fjdSER=r+YNjPHVCGqSs9wneT1CYnjtS8kF1d9UX9c49w@mail.gmail.com
Whole thread Raw
In response to Re: Are pgrpm changes for JDBC discussed here before submission?  (Vladimir Sitnikov <sitnikov.vladimir@gmail.com>)
Responses Re: Are pgrpm changes for JDBC discussed here before submission?
Re: Are pgrpm changes for JDBC discussed here before submission?
List pgsql-jdbc
Hey folks,

Thanks for the suggestions!
I was able to get around it with the following:

yum -y install java-1.8.0-openjdk-devel
yum -y install apache-maven
yum -y install jpackage-utils java-headless

# For my RHEL7 build:
export JAVA_HOME=/usr/lib/jvm/java-1.8.0-openjdk.x86_64/jre

And then in the spec file, I use:
mvn -DskipTests -P release-artifacts clean package

It seems to work.

I know that with the new 9.5.0 postgresql release in progress things are busy for the pgrpm's team, so I'm not sure if/when this patch would go in.

Regards,
  -John

On Tue, Jan 5, 2016 at 10:27 AM, Vladimir Sitnikov <sitnikov.vladimir@gmail.com> wrote:
I think Github tarballs are fine.
Tags with REL${version} are going to be the release tags.

To trigger toolchain usage (and disable enforcer at the same time),
you need to use `mvn package -Prelease` command.
However, it might be better to create -Pactivate-toolchains to make
that explicit.

Sample toolchains.xml file can be found in the source root of pgjdbc project.
You might want to add -DskipTests, otherwise you need to have a
running PostgreSQL instance to execute the tests.

Vladimir

pgsql-jdbc by date:

Previous
From: Vladimir Sitnikov
Date:
Subject:
Next
From: Dave Cramer
Date:
Subject: Re: Backend protocol wanted features