Everything in CAP / Java
Type
Domain: 2
Origin
Signals: SAP only
Content
Java: Answers in Java
More
Group by: Capability
Shows which feature branches reached which environment branch
A team that does not keep one long-lived branch per environment has no environment branches for it to compare feature branches against. What it reports is the merge state of branches in Git, so it says nothing about whether a merged change has been built or deployed to the environment.
Reads bound service credentials on SAP BTP, Cloud Foundry for CAP Java
Reads SAP BTP Operator service bindings on Kyma for CAP Java
Maven bill of materials pinning CAP Java module versions
Maven bill of materials pinning CAP Java module versions
Boolean and string flags read by applications at runtime
Maven bill of materials pinning CAP Java module versions
Collects Cloud Foundry or Kyma logs into a searchable Kibana
Ten short CAP Java references, one document per topic
Multitenancy for CAP Java: tenant lifecycle and per-tenant containers
Maven bill of materials pinning CAP Java module versions
Registers a multitenant application for subaccount subscriptions
Maven bill of materials pinning CAP Java module versions
Groups npm audit findings by root dependency, with failing thresholds
It audits through npm: a project that resolves its dependencies with another package manager, or has no `package.json`, has nothing for it to run. What it reports is what `npm audit` knows, so a vulnerability outside the npm advisory data is not in its table.
Predefined CI/CD pipelines for SAP development projects
Consumer side of a CAP Java parent pom promotion model with Renovate
Neither the package manifest nor the repository tree declares a licence.
Maven parent pom pinning cds-services-bom and Spring Boot for CAP Java
Neither the package manifest nor the repository tree declares a licence.
CLI of CAP development tools for Cloud Foundry workflows
There is no repository and no README: what the eight commands do is only readable from the compiled dist that ships in the package. Three of them — npmrc, install, project — are written for "SimpleMDG" projects rather than for CAP generally, so the reusable part is bind-local, run-local and debug. Seven releases up to July 2026. Its binding step writes the resolved VCAP_SERVICES into default-env.json in the project, where [@sap/cds-dk](artifact:sap-cds-dk) keeps only the place the credentials can be fetched from, so a project using it needs that file kept out of version control.
Switches Cloud Foundry API, org and space from a view in VS Code
Browser dashboard for a running CAP Java service during development
Maven plugin running CDS build steps in a CAP Java project
CAP Java service consuming a Business Partner API mocked in Node.js
Neither the package manifest nor the repository tree declares a licence.
Ten short CAP Java references, one document per topic
pnpm workspace running CAP, a local launchpad and two UI5 apps
Neither the package manifest nor the repository tree declares a licence.
Maven bill of materials pinning CAP Java module versions
Maven plugin running CDS build steps in a CAP Java project