Skip to content

Use explicit versioning for gradle-rxjava-project-plugin #2871

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

Merged
merged 1 commit into from
May 13, 2015

Conversation

davidmoten
Copy link
Collaborator

When a release is created the tagged version should build deterministically at any time. The wildcard dependency on gradle-rxjava-project-plugin in build.gradle means this will not be the case. This PR sets the version at 2.2.3 (the latest on Maven Central).

@davidmoten
Copy link
Collaborator Author

I'm curious to the delay on this PR, seems straightforward. @JakeWarton I'm going to quote you here from your gist :

Prevent wildcard versions in your Gradle project. These undermine deterministic and hermetic builds and are generally considered bad practice.

@quidryan Thought I'd check with you here seeing as you have done a lot of gradle build work with RxJava.

@benjchristensen
Copy link
Member

I'm curious to the delay on this PR

Just me.

wildcard versions in your Gradle project

We avoid them in actual project dependencies (of which we have none), but for the Gradle project plugins itself we were okay with it as we controlled both of them and it simplified build fixes.

I'm okay either way. Have you run into issues with the plugin?

benjchristensen added a commit that referenced this pull request May 13, 2015
Use explicit versioning for gradle-rxjava-project-plugin
@benjchristensen benjchristensen merged commit 03dd808 into ReactiveX:1.x May 13, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants