Historically, every now and then, and more so recently, the Opencast release artifacts aren't uploaded to Maven Central. This is bad because we depend on those. It's not so bad for local development, because you most likely have them in your local Maven cache anyway, but this is not the case in our CI.
Because of that, we currently build Opencast ourselves in the GitHub Workflow. That means that if we
Raise Opencast versions, we always have to keep that up to date as well, which is error prone. Also, the way it is written now suggest that it is optional, presumably only building Opencast when the artifact is missing from Maven Central, but that's not actually true; we always build (any version of) Opencast at least once (and then cache it).
Historically, every now and then, and more so recently, the Opencast release artifacts aren't uploaded to Maven Central. This is bad because we depend on those. It's not so bad for local development, because you most likely have them in your local Maven cache anyway, but this is not the case in our CI.
Because of that, we currently build Opencast ourselves in the GitHub Workflow. That means that if we
Raise Opencast versions, we always have to keep that up to date as well, which is error prone. Also, the way it is written now suggest that it is optional, presumably only building Opencast when the artifact is missing from Maven Central, but that's not actually true; we always build (any version of) Opencast at least once (and then cache it).