android,binder,cronet: .aar file when publishing (1.55.x backport) #10144
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.
Backport of #10138
The upgraded Android Gradle Plugin no longer played nice with the
android-maven-publish
plugin used earlier to produce Android library .aar files. No .aar files were being published at all.This removes the android-maven-publish plugin that is no longer needed with the newer version of AGP and updates the
grpc-android
,grpc-binder
andgrpc-cronet
to use the native Android library publishing features of AGP.Using the
grpc-android
project as an example, before these changes the files produced by the publishing step were:After the change get get:
The
diff
output from comparing the old POM with the new is: