Add Jitpack Publishing Support#4
Open
tternes wants to merge 2 commits intodeviceplug:masterfrom
Open
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR adds support for building and publishing the library with jitpack.io. Currently, it is necessary for release versions to be formally published or for developers to maintain complex build systems to generate this code for their applications.
This change allows libraries that depend on the Java portions of this library (like btleplug) to simply declare the implementation as a dependency in build.gradle:
In this example, a specific commit from my working fork is being specified. Tags, branches, etc. are also supported, giving end developers a lot of flexibility.