You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 3, 2022. It is now read-only.
Even this isn't in any kind of release state or anything, there's people using it.
Allowing Jitpack to build and publish the library would make it easier for dependants to import it, however would also give a false sense of "this isn't going to change and is an API" that isn't actually true (the mod version being 1.0.0 is just because I didn't feel like it needed an 0.x phase, not because the API is final).
However, I am (and will be) anyway checking enough for binary compatibility before pushing changes given I know this (until it's the latest requested changes by CaffeineMC at least), so that may not be as blocking other than it would remove the implicit warning of "there's no 'supported' builds". Plus that I don't want to add import instructions from "my" jitpack here, given I still don't consider this the project's home, so jitpack would just be "if you find it, use at your own risk", and would need to be removed in the final version given it'd get into a proper maven.
Even this isn't in any kind of release state or anything, there's people using it.
Allowing Jitpack to build and publish the library would make it easier for dependants to import it, however would also give a false sense of "this isn't going to change and is an API" that isn't actually true (the mod version being 1.0.0 is just because I didn't feel like it needed an 0.x phase, not because the API is final).
However, I am (and will be) anyway checking enough for binary compatibility before pushing changes given I know this (until it's the latest requested changes by CaffeineMC at least), so that may not be as blocking other than it would remove the implicit warning of "there's no 'supported' builds". Plus that I don't want to add import instructions from "my" jitpack here, given I still don't consider this the project's home, so jitpack would just be "if you find it, use at your own risk", and would need to be removed in the final version given it'd get into a proper maven.
Thoughts?