chore: crypto-ffi: don't use the base maven-publish plugin #903
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 base plugin is missing tasks to publish to Maven Central. Instead, use the high-level plugin, that provides those tasks, but still try to disable javadoc generation.
For POM information it looks like the high-level plugin picks up gradle.properties automatically, so we can remove the
bit. Actually, we have to remove it, because it's incompatible with the high-level plugin and using it results in an error.