Skip to content

Conversation

@wangmengyan95
Copy link
Contributor

  1. Update Parse to 1.10.1
  2. Update Bolts to 1.2.1
  3. Revise ParseLoginUI gradle to use absolute path not ext path, so when developers import it separately, there is no error due to no ext in developers's root gradle.

@hallucinogen
Copy link

Ship!

Choose a reason for hiding this comment

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

wait. Why it needs to change? Why not use rootProject.ext.bolts?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Because if developers import the ParseLoginUI to their project, in most of the cases, they do not have ext variable in their root gradle. So they have to manually copy them, which is not so convenient. Any thoughts?

Choose a reason for hiding this comment

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

I see. Sounds good then

wangmengyan95 added a commit that referenced this pull request Aug 30, 2015
…_1.10.1_and_update_ParseLoginUI_gradle

Update Parse to 1.10.1 and revise path for ParseLoginUI gradle
@wangmengyan95 wangmengyan95 merged commit 1ff315b into master Aug 30, 2015
@wangmengyan95 wangmengyan95 deleted the wangmengyan.update_Parse_to_1.10.1_and_update_ParseLoginUI_gradle branch August 30, 2015 21:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants