Skip to content
This repository has been archived by the owner on Feb 11, 2022. It is now read-only.

Gradle 3.5 support #115

Merged
merged 3 commits into from
Apr 14, 2017
Merged

Gradle 3.5 support #115

merged 3 commits into from
Apr 14, 2017

Conversation

passsy
Copy link
Contributor

@passsy passsy commented Apr 12, 2017

Fixes #112, #113

Upgraded gradle to 3.4.1 but since 3.5 was just released I upgraded to the latest version.
Upgraded AndroidLibrary.java to support the latest internal API changes.


I tried to solve it without using any internal APIs but AFAIK this would involve manual pom adjustments. This is all solved by the internal API.

@stefanhoth
Copy link
Contributor

Can one of the admins review this PR?


class AndroidLibrary implements SoftwareComponentInternal {

private final Usage runtimeUsage
private final UsageContext runtimeUsage
Copy link
Contributor

Choose a reason for hiding this comment

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

Are these changes going to work if the users of the plugin have gradle version older than 3.5? I guess with this, the library will require the users to use version 3.4?

Copy link
Contributor Author

@passsy passsy Apr 12, 2017

Choose a reason for hiding this comment

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

yes, it doesn't work with 3.3 and before. It works 3.4+

Copy link
Contributor

Choose a reason for hiding this comment

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

I guess it is fine as long as we make it clear on the release notes.

Copy link
Contributor

Choose a reason for hiding this comment

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

@tasomaniac I just update issue #112. I don't think we have other option than re-release for 3.4+ only. More details can be found here.

@stefanhoth
Copy link
Contributor

Why is the CI still using my token. 😡

@mr-archano
Copy link
Contributor

@stefanhoth it seems like a glitch. Apparently PRB has not been triggered at all.

@stefanhoth
Copy link
Contributor

Retest this please.

@stefanhoth
Copy link
Contributor

Ok to test.

@stefanhoth
Copy link
Contributor

Ok that was it. Sorry for the spam and thank you for the contribution @passsy!

@ouchadam
Copy link
Contributor

@mr-archano do you think it's worth throwing in the code if the version of gradle isn't 3.4+ or will a warning in the readme be enough?

@tasomaniac
Copy link
Contributor

@ouchadam it will fail anyways with mysterious error output. If we can detect the version of the gradle used, we can fail fast and tell them to update their gradle. Probably this will happen when they update our plugin. So it will be easier for them to update gradle too.

@passsy
Copy link
Contributor Author

passsy commented Apr 13, 2017

I'm absolutely for the gradle version detection with a good error message

@passsy passsy mentioned this pull request Apr 14, 2017
@tasomaniac tasomaniac merged commit cc98bcf into novoda:master Apr 14, 2017
@passsy passsy deleted the feature/gradle_3.5 branch April 14, 2017 14:30
passsy pushed a commit to GCX-HCI/ThirtyInch that referenced this pull request Sep 21, 2017
improves compatibily with Android Studio 3.0

Required upgrade of bintray plugin novoda/bintray-release#115
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.

5 participants