Closed atsushieno closed 3 years ago
alsakt is now available on Maven Central so it is non-issue regarding CI builds anymore. But I'm still wondering if it is feasible to add alsakt as a ktmidi-jvm dependency because then we may end up with WinMM/CoreMIDI dependencies as well, which may be kind of annoying for some usages (e.g. when some ktmidi app needs to inspect all the dependencies for some reason).
It is now unified and packages are published altogether as of 6621ae1.
ktmidi-jvm-desktop was split from here to avoid complicated package dependencies. Now that jitpack is not able to build this repository anymore (due to lack of chromeheadless test runner environment), we will have to resort to MavenCentral or whatever usable anyways. Once we choose a working repository that does not need any authentication (GitHub Packages is no-go in the end), we can bring back AlsaMidiAccess into this repository, adding alsakt as a dependency.