-
Notifications
You must be signed in to change notification settings - Fork 35
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
petitparser on maven central #15
Comments
FYI I forked here https://github.com/jgitver/java-petitparser/tree/jgitver and just pushed
It will find its way to central in the following minutes/hours once the synchronization between sonatype & central occur. |
Thank you, I'll give it another try to publish to Maven Central and let you know how it goes. Your changes and the links to working documentation will certainly help. Hopefully, things are simpler in the meantime :-) |
Perfect thank you for your reconsideration. |
Created a new project ticket: https://issues.sonatype.org/browse/OSSRH-43881 |
Managed to run |
I see it on Sonatype repo https://oss.sonatype.org/content/groups/public/com/github/petitparser/petitparser-core/2.2.0/ It should be on its way to central. |
Is there anything else I can / should do? |
Thank you for your help and your pushing on getting it there 👍 |
I know that #5 has been closed because of jitpack deployment but I would really like that you reconsider to publish the library on maven central.
Like you I provide some OSS libraries ; one of them is jgitver which consist of 3 projects:
The problem of jitpack, is as being a non standard repository, end users of plugins/libs have to declare in their build tool the usage of jitpack even if they just use 'plugins' and not directly your library.
This means for jgitver plugins that jitpack has to be present not just in the standard dependencies scope but also in the plugin dependencies scope:
pluginRepositories
setting for mavenbuildscript>repositories
setting for gradleHaving java-petitparser in central would just be transparent for any one using it anywhere in anytool.
Like many others I personally publish to central via sonatype. If you follow the instructions there (https://central.sonatype.org/pages/ossrh-guide.html) it is a no brainer.
Without a deployment to central, I see only 2 possibilities for me:
I am going to do 2. right now otherwise I cannot publish my latest version of the gradle plugin but I would really prefer to avoid any of the 2 mentioned possibilities.
Thanks for your understanding.
The text was updated successfully, but these errors were encountered: