Rename otp-shaded-jar
artifact and fix deployment to Maven Central
#6331
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.
Summary
Add back the shaded jar as an Maven artifact.
This will keep adding the "one-jar" as an artifact to Maven Central for the next release. The doc
is updated. I updated to the next version number where apropriate, since the path in Maven Central
will change. Therefore, the new path does not exist yet - it will exist when the next release (2.7.0) is made.
Issue
This is related to #6267
Unit tests
🟥 Not relevant.
Documentation
✅ All scripts and documentation referencing the shaded jar is updated.
Changelog
✅ This is relevant for everyone maintaining OTP deployments - so to "spreed the news" we will to include this
in the chagelog - even if it is not relevant to product owners.
Bumping the serialization version id
🟥 Not needed.