This repository was archived by the owner on Dec 29, 2022. It is now read-only.
Separate Java and Android builds #34
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Jul 7, 2016
Closed
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes issues #28 and #25, removes blocker from PR #24
This makes the root
pom.xmljust call out toandroid/pom.xmlandjava/pom.xmlwhich produce an Android AAR and a Java JAR respectively.The resulting libraries are:
com.firebase:geofire- just a POM that depends on the other two (useless, not sure how to stop it from publishing).com.firebase:geofire-java- library for Java server users.com.firebase:geofire-android- library for Android users.@AbeHaskins or @jdimond please review