Message-ID: <gh-pgjdbc-pgjdbc-4130@github.com>
From: "vlsi (@vlsi)" <noreply+vlsi@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Tue, 02 Jun 2026 08:59:41 +0000
Subject: [pgjdbc/pgjdbc] issue #4130: Refactor test-gss to a regular tests rather than a standalone app
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Id: 213894
X-GitHub-Author-Login: vlsi
X-GitHub-Issue: 4130
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-State: open
X-GitHub-Type: issue
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/issues/4130
Content-Type: text/plain; charset=utf-8

We have test-gss module written in Groovy, and it causes maintenance issues:
* It adds extra dependency (groovy-all) which is used in a single place only.
* It adds to dependency update PRs like https://github.com/pgjdbc/pgjdbc/pull/3648
* I requires to maintain separate Gradle config and binary jar: https://github.com/pgjdbc/pgjdbc/blob/301cfb7a5a1950eb9d545dcb4b8d13162bd4e855/test-gss/gradle/wrapper/gradle-wrapper.jar
* It requires extra command to launch the test

I have no hard feelings, however, `test-gss` would probably look better as an extra module or a class inside `pgjdbc/src/test/...`.

I can file a PR to harmonize the test if that is desired.

Any thoughts?