[pgjdbc/pgjdbc] 72dc69: Update waffle-jna to new artifact coordinates (#13...

From: Craig Ringer <craig(at)2ndquadrant(dot)com>
To: pgsql-jdbc(at)lists(dot)postgresql(dot)org
Subject: [pgjdbc/pgjdbc] 72dc69: Update waffle-jna to new artifact coordinates (#13...
Date: 2019-01-07 13:45:21
Message-ID: 5c3357f13a671_3ea52b238202a5781529ed@hookshot-fe-6e9b612.cp1-iad.github.net.mail
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

Branch: refs/heads/master
Home: https://github.com/pgjdbc/pgjdbc
Commit: 72dc692e1104a726385a9df10a4778f4e7e73020
https://github.com/pgjdbc/pgjdbc/commit/72dc692e1104a726385a9df10a4778f4e7e73020
Author: Craig Ringer <craig(at)2ndquadrant(dot)com>
Date: 2019-01-07 (Mon, 07 Jan 2019)

Changed paths:
M docs/documentation/head/connect.md
M pgjdbc/pom.xml

Log Message:
-----------
Update waffle-jna to new artifact coordinates (#1383)

* Update waffle-jna to new artifact coordinates

* Make docs more explicit about how to use SSPI

**NOTE:** This service has been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/

Functionality will be removed from GitHub.com on January 31st, 2019.

Browse pgsql-jdbc by date

  From Date Subject
Next Message Dave Cramer 2019-01-07 16:01:36 Re: setPortNumber() should not be used when useing connection fail-over feature with PGConnectionPoolDataSource?
Previous Message Okano, Naoki 2019-01-07 10:07:24 setPortNumber() should not be used when useing connection fail-over feature with PGConnectionPoolDataSource?