Skip to content

petitparser on maven central #15

Description

@McFoggy

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:

  • 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:

  1. refactor to remove the usage of java-petitparser
  2. 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.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions