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

Publish on maven repo #6

Closed
electronstudio opened this issue Apr 9, 2020 · 8 comments · May be fixed by #18
Closed

Publish on maven repo #6

electronstudio opened this issue Apr 9, 2020 · 8 comments · May be fixed by #18
Labels
enhancement New feature or request

Comments

@electronstudio
Copy link
Owner

Publishing on Jitpack is quite easy, but since I'm not using this project for anything yet I haven't done it. JCentral would be better but is perhaps more work.

@electronstudio electronstudio added the enhancement New feature or request label Apr 9, 2020
@mores
Copy link
Contributor

mores commented Nov 30, 2020

Would you like some help in getting this published to a maven repo ?

@ewpratten
Copy link

This would save me so much work when I use this library. I only have experience setting up JitPack for Gradle projects though, so I will not be able to make a good PR for this.

You could also look into using the GitHub Packages Repository, which allows you to publish JARs via curl if you really wanted

@ewpratten
Copy link

On second thought, I'm going to look in to making a PR for this

@electronstudio
Copy link
Owner Author

electronstudio commented Sep 20, 2021

Plan for this:

  • Upload current jars to Cloudsmith repo
  • Make example project
  • Make video showing beginners how to use example project?
  • Switch (as much of build as possible, doesnt have to be all at once) to use Maven
  • Sign up for Maven Central
  • Produce better Javadoc jar (can we extract the doc strings from raylib.h ?)
  • Use Maven to publish on Maven Central

@rutenkolk
Copy link

rutenkolk commented Dec 15, 2021

Maybe display the 4.0.0-0 version more prominently somewhere.

There are tools like leiningen which while allowing ranges, warn you heavily when you do. Leiningen for example is the most prominent build-tool in clojure, which makes this version of the library somewhat inaccassible for the clojure programming language. I would wager most leiningen users have never touched version ranges.

@electronstudio
Copy link
Owner Author

Version number is displayed under releases, not sure where else anyone would look for it.

For Gradle I suggest using 4.0.+ because if I put out at 4.0.0.1 (or if Raylib upstream does a 4.0.1) then it will be a bug fix release and I assume most people would want it immediately. I wouldn’t suggest using 4.+ because Raylib API is not backwards compatible so you probably won’t want your project to change to Raylib 4.1 unexpectedly.

Users are free to use whatever tools and ranges they like of course.

@rutenkolk
Copy link

whoops. My bad. I didn't see the releases page 🤦‍♀️

I just read the readme.

@electronstudio
Copy link
Owner Author

Not fully automated, but now publishing on maven central.

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

Successfully merging a pull request may close this issue.

4 participants