From: Krzysztof B. <kb...@un...> - 2020-06-28 10:58:42
|
Dear Subscribers, [This notice is relevant only for Unity users who are /developing against Unity //Java//APIs/] As you could noticed the delay between 3.2 and an upcoming 3.3 release was bigger than usual. It was caused partially by an undertaken effort to move Unity from the Maven repository hosted by courtesy of Forschungszentrum Jülich to the Maven Central. That was a complex process as many of Unity dependencies where also hosted there. With Bernd's support, we managed to migrate all Unity dependencies to GitHub from Sourceforge, and we have deployed them to Maven Central. Hopefully this means that from the next Unity release all Unity artefacts will be available from the most popular repository in JVM ecosystem. This brings many benefits: I'd like to express here my gratitude to FZJ for hosting Unity Maven repo, free of charge, for something around 7 years, and more personally pass big thanks to Bernd, who helped with the whole action of moving to GitHub and Maven Central. Technically the move to Maven Central Repository required us to change Maven's groupId of all Unity artifacts (as well as few dependencies that we maintain). From Unity version 3.3.0 all Maven artifacts will live in the group "io.imunity". Artifact ids were not modified, version numbers are continued. Best, Krzysztof |