For the m2 build we need a few dependencies (e.g. org.eclipse.emf.transaction, org.eclipse.emf.validation) that are traditionally available via p2 update sites (only).
To be able to provide a m2 version of the modelserver we use very outdated versions of those dependecies, provided via a wso2 mirror. See for example https://maven.wso2.org/nexus/content/groups/wso2-public/org/eclipse/org.eclipse.emf.transaction/
We discussed that matter in the past already, and probably it will be necessary now to host our own maven dependency under the emfcloud namespace.
The main drawbacks of the current situation:
Obivously the very outdated versions of those dependencies without any chance to update the version at the moment.
We are dependent on the stability of the wso2 mirror, which may result in build instabilities on the CI instances and also affects the development experience of contributors/developers/users of the modelserver project.
For the
m2build we need a few dependencies (e.g.org.eclipse.emf.transaction,org.eclipse.emf.validation) that are traditionally available via p2 update sites (only). To be able to provide am2version of the modelserver we use very outdated versions of those dependecies, provided via a wso2 mirror. See for example https://maven.wso2.org/nexus/content/groups/wso2-public/org/eclipse/org.eclipse.emf.transaction/We discussed that matter in the past already, and probably it will be necessary now to host our own maven dependency under the
emfcloudnamespace. The main drawbacks of the current situation: