Skip to content
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

Maven Central #19

Open
edrevo opened this issue Mar 11, 2022 · 2 comments
Open

Maven Central #19

edrevo opened this issue Mar 11, 2022 · 2 comments

Comments

@edrevo
Copy link

edrevo commented Mar 11, 2022

Many thanks for open sourcing this great library! Would you consider uploading it to Maven Central? I can't add jitpack as a maven repository in some of the projects I'd like to use this lib, unfortunately.

@jimblackler
Copy link
Owner

I would consider it but it'll have to go on the to do list because I've a bit of a backlog and haven't uploaded anything there before.

@jmini
Copy link

jmini commented May 17, 2022

I can help you with the setup. Ping me.

You will need:

From a build point of view:

  • you will need following plugins:
    • id 'signing' to sign your artifacts
    • id 'io.github.gradle-nexus.publish-plugin' to manage the publication on sonatype
  • Optionally:
    • I am also using id 'net.researchgate.release' to change the version (management of -SNAPSHOT suffix) and tag the version
  • I did not do a complete review, but some other
    • version management: in a lot of project the version is a.b.c-SNAPSHOT while you develop. Maybe it is not compatible with jitpack. And it it is changed too a.b.c when you create the release. And then it is bumped to a.b.(c+1)-SNAPSHOT to work on the next version.
    • some changes to the generated pom to add some required sections.

Ping me if you need more details.
There are also tons of tutorials on the web.


What you could also consider is joining an existing organization like the one I am participating to: https://github.com/OpenAPITools (I did not ask if this would be possible, In my opinion OpenAPI and JSON-Schema are related topics).
All the administrative tasks are already solved and you would join an helpful community. But I can understand that you prefer keeping full ownership on your project. (I also have the setup to publish on maven central my own side projects -- not shared with the community)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants