While I do like jitpack.io, I can't really ignore two things:
1.) some people say that Jitpack taking the source and creating unsigned AARs is a security liability, but would still not grab the source code and put it in their code directly because it is objectively a hassle to do. Still, this prevents the library from being used by certain organizations.
2.) Jitpack has noticeable downtimes that MavenCentral never has.
If someone is on a new machine, and the library is not cached, they can easily be stuck for a while, waiting for Jitpack to recover.
This is quite a problem. So if one were to figure out how to actually make MavenCentral host libraries (i do own zhuinden.com so it is not actually a problem), then the latest versions of Simple-Stack and accompanying libraries (simple-stack-extensions, simple-stack-compose-integration, state-bundle) should be rehosted on MavenCentral.
A reference implementation for hosting on MavenCentral might be found here:
https://github.com/requery/sqlite-android/pull/169/files
While I do like jitpack.io, I can't really ignore two things:
1.) some people say that Jitpack taking the source and creating unsigned AARs is a security liability, but would still not grab the source code and put it in their code directly because it is objectively a hassle to do. Still, this prevents the library from being used by certain organizations.
2.) Jitpack has noticeable downtimes that MavenCentral never has.
If someone is on a new machine, and the library is not cached, they can easily be stuck for a while, waiting for Jitpack to recover.
This is quite a problem. So if one were to figure out how to actually make MavenCentral host libraries (i do own
zhuinden.com
so it is not actually a problem), then the latest versions of Simple-Stack and accompanying libraries (simple-stack-extensions
,simple-stack-compose-integration
,state-bundle
) should be rehosted on MavenCentral.