GSS: reuse existing Subject and GssCredentials
Escape schema name when setting search_path
Add tests for schema name containing special characters
Setting the search_path from currentSchema property is done in startup packet (v3 protocol only)
Using setStringType on DataSource correctly set the associated Connection property
Honor stringtype=unspecified when also saving null values
Merge pull request #201 from simkam/eap_krb_2

gssapi: Re-use existing Subject and GssCredentials

The current implementation of `MakeGSS.java` always calls JAAS directly. In managed environments like application servers an upper level layer can handle authentication and then call `Driver.connect`. PgJDBC may not have access to the raw GSS credentials, or may be requiring the user to unnecessarily repeat them when the upper layers already have this information.

Allow PgJDBC to query the `AccessControllerContext` for GSS credentials and, if found, use existing credentials. If no `AccessControllerContext` exists, proceed as before, acquiring credentials directly.
Merge pull request #207 from sehrope/search-path-escaping

Escape search_path in Connection.setSchema(...)
Merge pull request #216 from alexismeneses/ISSUE_155

Setting search_path in startup packet
Merge pull request #223 from byronvf/master

Honor stringtype=unspecified when also saving null values

Currently, saving a string with setString applies oid.UNSPECIFIED, but saving null with setNull(index, java.sql.Types.VARCHAR) saves with oid.VARCHAR.

For consistency, if the user requested that we treat string types as unspecified, we should do so in all cases.
Merge pull request #221 from alexismeneses/ISSUE_192

Fix for setStringType in DataSource
Add path for custom source repository of mvn dependencies

This commit adds two parameters making possible to specify a custom
remote repository from which are fetched dependent packages needed
for the build:
- maven.remote.repository.id to define the id of the remote repository
- maven.remote.repository.url to define the URL of the remote repository
Default values make process point to the central Maven repository, but
those values can be enforced using build.local.properties.