Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[bundletool] bump to 0.10.0 #3318

Merged
merged 1 commit into from
Jul 5, 2019

Conversation

jonathanpeppers
Copy link
Member

Context: https://github.com/google/bundletool/releases/tag/0.10.0
Context: https://mvnrepository.com/artifact/com.android.tools.build/bundletool

bundletool has had a few releases lately, we should update the
version we are shipping with Xamarin.Android.

I also noticed we were shipping:

bundletool-all-0.8.0-jar

I think we could just use bundletool.jar. It would be useful to have
a static filename as versions change release to release. This matches
up with other things we ship, such as r8.jar.

You can query the version of bundletool with:

$ java -jar bundletool.jar version
0.10.0

So we don't need to encode the version in the filename.

Context: https://github.com/google/bundletool/releases/tag/0.10.0
Context: https://mvnrepository.com/artifact/com.android.tools.build/bundletool

`bundletool` has had a few releases lately, we should update the
version we are shipping with Xamarin.Android.

I also noticed we were shipping:

    bundletool-all-0.8.0-jar

I think we could just use `bundletool.jar`. It would be useful to have
a static filename as versions change release to release. This matches
up with other things we ship, such as `r8.jar`.

You can query the version of `bundletool` with:

    $ java -jar bundletool.jar version
    0.10.0

So we don't need to encode the version in the filename.
Copy link
Contributor

@dellis1972 dellis1972 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks ok. Not sure why we didn't just use bundletool.jar for the file name in the first place lol

@jonpryor jonpryor merged commit b6b0491 into dotnet:master Jul 5, 2019
jonpryor pushed a commit that referenced this pull request Jul 22, 2019
Context: https://github.com/google/bundletool/releases/tag/0.10.0
Context: https://mvnrepository.com/artifact/com.android.tools.build/bundletool
Context: https://ossmsft.visualstudio.com/_oss?requestId=1728210&_a=progress

`bundletool` has had a few releases lately, we should update the
version we are shipping with Xamarin.Android.

I also noticed we were shipping:

	bundletool-all-0.8.0-jar

I think we could just use `bundletool.jar`. It would be useful to have
a static filename as versions change release to release. This matches
up with other things we ship, such as `r8.jar`.

You can query the version of `bundletool` with:

	$ java -jar bundletool.jar version
	0.10.0

So we don't need to encode the version in the filename.
jonpryor pushed a commit that referenced this pull request Jul 22, 2019
Context: https://github.com/google/bundletool/releases/tag/0.10.0
Context: https://mvnrepository.com/artifact/com.android.tools.build/bundletool
Context: https://ossmsft.visualstudio.com/_oss?requestId=1728210&_a=progress

`bundletool` has had a few releases lately, we should update the
version we are shipping with Xamarin.Android.

I also noticed we were shipping:

	bundletool-all-0.8.0-jar

I think we could just use `bundletool.jar`. It would be useful to have
a static filename as versions change release to release. This matches
up with other things we ship, such as `r8.jar`.

You can query the version of `bundletool` with:

	$ java -jar bundletool.jar version
	0.10.0

So we don't need to encode the version in the filename.
jonpryor added a commit that referenced this pull request Jul 22, 2019
This reverts commit ea13bec.

Oops; this was to be applied to d16-3, not d16-2.
@github-actions github-actions bot locked and limited conversation to collaborators Jan 30, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants