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

Update build and configuration to latest. #81

Closed
wants to merge 1 commit into from
Closed

Conversation

JakeWharton
Copy link
Member

Refs #47.

@JakeWharton
Copy link
Member Author

Sigh. Groovy. You're the worst.

@JakeWharton
Copy link
Member Author

Ping @mttkay @hamidp or anyone else that enjoys pain...

@JakeWharton
Copy link
Member Author

We need to nuke this rxjava-project plugin from orbit...

@mttkay
Copy link
Collaborator

mttkay commented Nov 27, 2014

I wrestled with this in the past. Isn't it more the Android plug in that's
to blame though? I recall that it was not based on the Java plug in for
Gradle, thus making it incompatible with the entire existing plug in
ecosystem by design. Smooth move. I talked to Xavier about this at IO this
year and he said they're aware of this and are looking to address this by
end of this year or early next year, as the major blocking thing (being
able to define multiple source sets to support Android's concept of build
flavors) has been added to Gradle core or will be added soon.

Meanwhile, @quidryan has been very helpful so far in alleviating build
pain. Maybe he can help?
On Nov 27, 2014 7:58 AM, "Jake Wharton" notifications@github.com wrote:

We need to nuke this rxjava-project plugin from orbit...


Reply to this email directly or view it on GitHub
#81 (comment).

@JakeWharton
Copy link
Member Author

Well to be fair, the Java plugin is basically crap. The Android version is
vastly superior in its internal model and Gradle will be adopting most or
all of its design in the future.
On Nov 26, 2014 11:21 PM, "Matthias Käppler" notifications@github.com
wrote:

I wrestled with this in the past. Isn't it more the Android plug in that's
to blame though? I recall that it was not based on the Java plug in for
Gradle, thus making it incompatible with the entire existing plug in
ecosystem by design. Smooth move. I talked to Xavier about this at IO this
year and he said they're aware of this and are looking to address this by
end of this year or early next year, as the major blocking thing (being
able to define multiple source sets to support Android's concept of build
flavors) has been added to Gradle core or will be added soon.

Meanwhile, @quidryan has been very helpful so far in alleviating build
pain. Maybe he can help?
On Nov 27, 2014 7:58 AM, "Jake Wharton" notifications@github.com wrote:

We need to nuke this rxjava-project plugin from orbit...


Reply to this email directly or view it on GitHub
#81 (comment).


Reply to this email directly or view it on GitHub
#81 (comment).

@mttkay
Copy link
Collaborator

mttkay commented Dec 3, 2014

Needs a rebase. Should get this in first, then finally land the samples rework...

@plastiv plastiv mentioned this pull request Dec 14, 2014
@JakeWharton JakeWharton deleted the jw/latest-build branch February 26, 2015 06:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants