JCenter Deprecation
MarkRS-UK opened this issue · 6 comments
With the imminent closure of jcenter as a repo, isn't it a problem that this (excellent library :-) ) still uses it?
Android Studio (& therefore presumably Intellij IDEA) now recommend removing jcenter... compilations using this library fail when that happens
I guess I'll upload the library and plugin to another repository. Any suggestions?
It's not something I know much about, only from the build files for my Android app :)
Maven seems to be the place,,, does that even make sense as a sentence?
So I notice your Flutter plugin is recommending forking the repo and using that. Is that to sidestep the jCenter closedown?
Would that be the best strategy here too?
The flutter plugin works over an explicit C++ file that can (should) be customized. That's why I recommend making a "private" fork before using it.
The original native implementation in Android works over .so compiled files.
I plan to move this library and its plugin to a new repository in the next few days. ;)
If you need a quick solution, you can download both .aar files (library and plugin) and use them locally.
Migrating to Maven Central started, tickets open:
I've published a new version with a new implementation. The documentation is up to date.
https://github.com/StringCare/AndroidLibrary/wiki/Implementation
Also, the KotlinSample project is updated.
Thanks for your patient @MarkRS-UK 😄