add sections to pom.xml required for publishing to maven central #6
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
| <url>https://github.com/docopt/docopt.java</url> | ||
| <description>Java port of docopt</description> | ||
|
|
||
| <parent> |
There was a problem hiding this comment.
This method has been deprecated because it pulls in any information that isn't overridden here. Best practice now is to copy/paste the repository and profile from oss-parent into this pom file.
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.
In order to publish artifacts to Maven Central via the Sonatype OSSRH route, certain sections must be added to the pom. One is the OSSRH parent pom, which contains the adequate repositories to use. Another is a license section. Also, source and javadocs should also be uploaded so I've added those plugins as well.
The scm connection is required by the release plugin which is the recommended way for performing the releases.
Lastly, GPG signing is required for artifacts. Adding this to the normal project lifecycle would break most builds if gpg is not installed or configured. Instead, I've added this to a
releaseprofile, which also gets automatically activated by theperformReleaseproperty, which causes it to be automatically activated when using thereleaseplugin.I hope this helps expedite the process to get this officially into Central.