-
Notifications
You must be signed in to change notification settings - Fork 138
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use npm workspaces to reuse @sap/cds-mtxs from MTX Sidecar #228
Conversation
Aligned MTA deployment files and MTX Sidecar with best practices Introduced workspaces concept for mtx/sidecar to ensure availability of @sap/cds-mtxs in root node_modules
This reverts commit 3be6b5c.
Follow up of #224 |
I've just noticed that the
After deleting the
|
@LotharBender Hi Lothar, yes this behavior is described here: https://cap.cloud.sap/docs/java/assets/cds-maven-plugin-site/install-cdsdk-mojo.html: By default, this goal looks for an already installed @sap/cds-dk and skips installation if it was found. It doesn't validate the found version against the requested version and the existing @sap/cds-dk could be outdated. Add property -Dcds.install-cdsdk.force=true to the Maven command line to force the installation of the @sap/cds-dk in the configured version. |
But doesn't this again prove that Java projects should better stick to the npm approach of maintaining and updating npm dependencies instead of using a maven based mechanism?
On the other hand this means that the default local development experience of the current cds-dk installation approach is not better than using |
Newer proposal: #346 |
npm workspaces can help to share @sap/cds-mtxs from MTX Sidecar with the version used by @sap/cds-dk and cds build.
Main downside at the moment: To retain fixed versions when using @sap/cds-dk this requires a package-lock.json in root.
In addition the package-lock.json in mtx/sidecar is required for cds build, as only this file is copied over to gen.