jaylib icon indicating copy to clipboard operation
jaylib copied to clipboard

Publish on maven repo

Open electronstudio opened this issue 5 years ago • 8 comments

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 avatar Apr 09 '20 14:04 electronstudio

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

mores avatar Nov 30 '20 18:11 mores

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 avatar Jan 03 '21 16:01 ewpratten

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

ewpratten avatar Jan 03 '21 17:01 ewpratten

Plan for this:

  • [x] Upload current jars to Cloudsmith repo
  • [x] Make example project
  • [x] 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
  • [x] 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

electronstudio avatar Sep 20 '21 16:09 electronstudio

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.

rutenkolk avatar Dec 15 '21 22:12 rutenkolk

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.

electronstudio avatar Dec 16 '21 15:12 electronstudio

whoops. My bad. I didn't see the releases page :woman_facepalming:

I just read the readme.

rutenkolk avatar Dec 16 '21 16:12 rutenkolk

Not fully automated, but now publishing on maven central.

electronstudio avatar Jul 10 '22 11:07 electronstudio