Example config for publishing to Maven Central #375
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.
This PR adds some example config for publishing to Maven Central.
I'm pleased to say that the publishing process is now a lot more pleasant than it was a few years ago. Sonatype really worked on the DX!
But there are some problems:
Parent POM
I removed the inheritance from the parent POM because it is defining the distribution repository to be camsys-apps.com but we don't want that. If you want to keep using the parent POM then you'd have to change a few things there.
Upload limit
The combined upload to Maven Central is 1.5 GB big which is above the size limit:
https://central.sonatype.org/publish/publish-portal-upload/
I'm not familiar with all these components but there are quite a few *-webapp modules that build large WAR files which are around 200MB each. Are these supposed to be published to Maven Central?
Because of the last point, I haven't actually succeeded in uploading the artifacts.
For reference, this is the command I executed for the deployment:
cc @aaronbrethorst