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

Updated the way build.gradle resolves subprojects for android #16

Closed
wants to merge 1 commit into
base: master
from

Conversation

Projects
None yet
1 participant
@dant3
Copy link

dant3 commented Feb 24, 2015

This fixes build problems then you add smack as submodule and subproject to your own gradle based project.
The build failed because the project paths/names were absolute and thus, were only correct if smack was a root project.
Now it doesn't matter if smack is root project or not as subprojects are looked up relatively (by directory name).

Updated the way build.gradle resolves subprojects for android
This fixes build problems then you add smack as submodule and subproject to your own gradle based project.
The build failed because the project paths/names were absolute and thus, were only correct if smack was a root project.
Now it doesn't matter if smack is root project or not as subprojects are looked up relatively (by directory name)

@dant3 dant3 closed this Feb 24, 2015

@dant3

This comment has been minimized.

Copy link
Author

dant3 commented Feb 24, 2015

Forget about it, it looks like gradle is broken since some time in that it does not treats settings.gradle of subprojects of root gradle project, and so this won't work anyway.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment