Add configuration to publish to maven central #11
Conversation
This file contains 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
Upgrade to gradle 6.0.1.
hanleyt
force-pushed
the
add-config-to-publish-to-maven-central
branch
from
642b9b9 to
1a3b56c
Compare
Closed
…y're not present on travis. Update readme also.
Codecov Report
@@ Coverage Diff @@
## master #11 +/- ##
=======================================
Coverage 100% 100%
Complexity 13 13
=======================================
Files 1 1
Lines 42 42
Branches 2 2
=======================================
Hits 42 42Continue to review full report at Codecov.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 is to resolve longstanding request #3
Delete gradle legacy publishing, and upgrade to Gradle 6.0.1 for easier way to package sources and javadoc and new way to publish artifacts.