RUMM-2095: Support new AGP publishing model #916
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
0xnm
force-pushed
the
nogorodnikov/rumm-2095/support-new-agp-publishing-model
branch
from
54fd7eb to
d7ea8d1
Compare
xgouchet
approved these changes
Apr 29, 2022
mariusc83
approved these changes
Apr 29, 2022
0xnm
deleted the
nogorodnikov/rumm-2095/support-new-agp-publishing-model
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What does this PR do?
This change brings support of the new publishing model by explicitly specifying components for publishing (
releasein our case).This new model landed originally in AGP 7.1 and automatic components creation for publishing will be disabled in AGP 8.0.
Docs for the new approach can be found here.
Since new model can also attach
sourcesandjavadoc(byDokka) artifacts to the published component, explicit tasks for the sources and docs are removed.Change is verified by publishing to the local Maven, everything is fine and file set is complete (
aar+sources+javadoc+pom+module) and has an expected content.Review checklist (to be filled by reviewers)