petitparser on maven central
See original GitHub issueI 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:
- a library jar using java-petitparser; built with maven
- a maven plugin as a core maven extension; built with maven
- a gradle plugin; built with gradle
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:
- thus a specific
pluginRepositories
setting for maven - a specific
buildscript>repositories
setting for gradle
Having 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:
- refactor to remove the usage of java-petitparser
- fork, relocate under fr.brouillard.oss, and publish to central so that it is available out of the box as a resolvable dependency in maven & gradle.
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.
Issue Analytics
- State:
- Created 5 years ago
- Comments:9 (5 by maintainers)
Thank you for your help and your pushing on getting it there 👍
no perfect, your lib is on central