-
Notifications
You must be signed in to change notification settings - Fork 17
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
Comments
Would you like some help in getting this published to a maven repo ? |
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 |
On second thought, I'm going to look in to making a PR for this |
Plan for this:
|
Maybe display the 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. |
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. |
whoops. My bad. I didn't see the releases page 🤦♀️ I just read the readme. |
Not fully automated, but now publishing on maven central. |
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.
The text was updated successfully, but these errors were encountered: