Prepare Jenkins for Release to Maven Central for BaSyx Java V2
Summary
Releasing the Jar artifacts of BaSyx Java V2 to Maven Central is not possible. The reason for this is most likely that our artifact id changed with V2 from "org.eclipse.basyx" to "org.eclipse.digitaltwin.basyx" due to migrating to the Digital Twin toplevel project.
Steps to reproduce
Trigger BaSyx V2 build pipeline in the BaSyx Jenkins instance.
Relevant logs and/or screenshots
Failing release run: https://ci.eclipse.org/basyx/job/BaSyx%20V2/2/console
Priority
-
Urgent -
High -
Medium -
Low
Severity
-
Blocker -
Major -
Normal -
Low
Impact
This is blocking any upcoming release of BaSyx Java V2, including a milestone release.