Allow using custom bundletool jar #461
Merged
Conversation
This file contains hidden or 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
…ature/custom-bundletool
…ature/custom-bundletool
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.
This pull request introduces the ability to specify a custom Bundletool Java archive when running
android-app-bundletool actions, or specifying desired default bundletool path via Python API if the installation does not include data files. This allows users to use more recent version of bundletool than what is bundled together with the installation.This change is to support some advanced use cases where the default bundletool may not suffice, such as requiring specific bug fixes or experimental features present in custom builds.
Changes to CLI actions:
android-app-bundleactions accept optional argument--bundletoolto specify Bundletool jar to be used. If not given, the default included jar will be used instead as it used to be.android-app-bundle bundletool infoto show information about used Bundletool (Java runtime, Bundletool path and Bundletool version).android-app-bundle bundletoolwith actionsinfoandversionwas added to show information about the exact Bundeltool that is being used to carry out actions.android-app-bundle bundletool-versionis deprecated in favor ofandroid-app-bundle bundletool version. Old version acts as an alias for the new one for the time being with a relevant deprecation message.Screenshots of usage
Using included bundletool:
Using custom bundletool:
