SampleSampletypeA worked example you read or clone. Evidence: it demonstrates, it never provides.See every one →What this type is →independently maintainedindependently maintainedoriginPublished by one person or a small company outside SAP. Says nothing about quality; the readings say that.See every one →Starting point

cap-java-parent-pom-sample

A Maven parent pom published to GitHub Packages that pins cds-services-bom, the Spring Boot BOM and a shared CAP Java plugin, so a child application names the parent coordinate and no versions of its own.

com.example.central:central-parent holds the versions in dependencyManagement — cds-services-bom 4.8.0, spring-boot-dependencies 3.5.11 and emoji-plugin 1.2.0 — and the Maven plugin versions and JDK 21 in pluginManagement, so a child writes the parent coordinate with an empty relativePath and its own executions, and no version numbers. <repositories> is left out deliberately: a child has to know where to fetch the parent before it can read the parent, so the GitHub Packages address cannot be bootstrapped from the pom and goes into ~/.m2/settings.xml as a wildcard. A release bumps the pinned library version and the parent's own <version> together, because re-publishing one version to GitHub Packages answers 409 Conflict. It is the upstream half of the promotion model cap-java-child documents and tests. Written in Japanese.

Facts

Last push

Where it sits

Lives in
Demonstrates
CI/CD pipelinesCAPCI/CD pipelinescapabilityA pipeline that builds, tests and delivers an application each time its source repository changes, with a build log that shows which step failed. [Deployment](capability:deployment) describes getting the build onto its target runtime.
Flavors

Who is behind it

Mio YasutakeMio YasutakePersonMaintains this
In the atlas: maintains 47, contributes to 47, wrote 10
@miyasuta
maintainer

Before choosing this

Signals

LicenceNo licenseNeither the package manifest nor the repository tree declares a licence

Without a licence the default is all rights reserved. Ask the maintainer, or check for terms stated elsewhere, before depending on it.

What it declares

Every artifact

Type
Sample
Origin
Independently maintained
Runtime
Java

As a sample

Form
does not say

Connections1

cap-java-parent-pom-sample connectionscap-java-parent-pom-samplePROVIDES→ demonstrates1demonstrates authoredCI/CD pipelines

README

quoted from miyasuta/cap-java-parent-pom-sample, read
miyasuta/cap-java-parent-pom-sample/README.mdOn GitHub

central-parent(中央ビルド親pom)

複数の CAP Java アプリ(consumer)が <parent> 座標参照だけで依存ライブラリの版を継承するための中央親pom。 依存版を一元管理し、親pom を固定版で publish するだけで、子は pom 無変更(版指定なし)で新しい依存を取り込めることを目的とする。

  • 座標:com.example.central:central-parent
  • publish 先:GitHub Packages(https://maven.pkg.github.com/miyasuta/cap-java-parent-pom-sample)
  • 現行版:2.1.0(emoji-plugin 1.2.0 を pin)

「事前検証済みライブラリの版上げを手動確認なしで全 consumer に自動展開する」昇格モデルの上流。仕組み全体は consumer 側ドキュメント cap-java-child / GUIDE-promotion-model.md を参照。

excerpt, no licence read, read the rest, on GitHub

Details

Sources3
GitHub APIdiscovered here, miyasutachecked
github.com/miyasuta/cap-java-parent-pom-sampletree, pushes, contributors, CIchecked
README.mdquoted, and what the entry declareschecked

Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.

Compatibility and provenance
runtimesjava
discovered viaGitHub API · miyasuta
first seen in the atlas
ecosystem and domaincap, developer-experience
Flavors1
Java
“複数の CAP Java アプリ(consumer)が `<parent>` 座標参照だけで**依存ライブラリの版を継承**するための中央親pom。” — central-parent(中央ビルド親pom) — cap-java-parent-pom-sample READMEchecked
History in the atlas1
  1. First seen.
For your agent
Ref
artifact:miyasuta-cap-java-parent-pom-sample
JSON
/artifacts/miyasuta-cap-java-parent-pom-sample.json
MCP
Connecting an agent