Cannot publish anymore java artefacts on Jitpack

[kermitt2]

Jitpack now fails:

Git error. Max repo size 500MB exceeded

This is painful, because the artefacts themselves are just 15MB for the jar and 76MB for the one-jar. The git history will continue to grow...

So It seems we have to publish to maven central :(

[kermitt2]

Dear @chrismattmann and @sujen1412

Sorry to bother, I am trying to get things alright to publish the java artefacts in maven central via Gradle and so on.

Could you add a comment validating my request to Sonatype here: https://issues.sonatype.org/browse/OSSRH-80067 (otherwise apparently I am blocked !)

Many thanks in advanced and all the best from Grobid :)

[sujen1412]

No worries, its done. Thanks!

[kermitt2]

Thank you @sujen1412 !!

[kermitt2]

... set-up everything in branch https://github.com/kermitt2/grobid/tree/maven-central

This is incredibly time consuming... There are also different URLs to upload stuff either as release or snapshot, not sure how to manage that with gradle.

Snapshot/staging deployment and signing work, but for Grobid, javadoc is failing due to numerous comments with invalid characters - indeed javadoc is out of scope for Grobid as a choice. So the OSSRH repo validation step will fail anyway for an actual publication because there is no javadoc. Well it will fail for sure for this reason and maybe for other reasons :)

We could focus on a release of version 0.7.2 on maven central, which requires to fix all the issues with javadoc :/