Skip to content

Migrate flume-project hierarchy to logging-parent#464

Merged
ppkarwasz merged 1 commit into
trunkfrom
feat/logging-parent-migration
Jul 22, 2026
Merged

Migrate flume-project hierarchy to logging-parent#464
ppkarwasz merged 1 commit into
trunkfrom
feat/logging-parent-migration

Conversation

@ppkarwasz

Copy link
Copy Markdown
Member

Flume requires two POM hierarchies:

  • flume-dependencies and flume-third-party-dependencies are published flattened, so their common metadata can live in the aggregator flume-project, which is not published.
  • flume-parent is reused by satellite repositories, so it needs to be published. To avoid an excessive inheritance chain, it extends logging-parent directly instead of flume-project.

Flume requires two POM hierarchies:

- `flume-dependencies` and `flume-third-party-dependencies` are published flattened, so their common metadata can live in the aggregator `flume-project`, which is **not** published.
- `flume-parent` is reused by satellite repositories, so it **needs** to be published. To avoid an excessive inheritance chain, it extends `logging-parent` directly instead of `flume-project`.

Assisted-By: Claude Fable 5 <noreply@anthropic.com>
@ppkarwasz
ppkarwasz merged commit 14da304 into trunk Jul 22, 2026
4 checks passed
@ppkarwasz
ppkarwasz deleted the feat/logging-parent-migration branch July 22, 2026 18:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants