[CONJ-1053] Make the JPMS requirement on waffle-jna static #185
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The waffle-jna dependency is needed only when Windows GSSAPI authentication is used. In a previous commit, the
static
was incorrectly removed, making the dependency a hard requirement when running on JPMS.5ac67b2
However, maven is not the same as JPMS. An optional dependency via Maven is not the same as
requires static
in JPMS. They serve entirely different purposes. By removingrequires static
, you are saying that all deployments must have waffle-jna present on the module path.Re-adding
requires static
will not affect existing clients using MariaDB Connector-J. If they used waffla-jna before, they will continue to use it after this change.https://jira.mariadb.org/browse/CONJ-1053