-
Notifications
You must be signed in to change notification settings - Fork 242
build: centralize module versions in a shared parent POM - #645
Open
fabisev wants to merge 1 commit into
Open
Conversation
Stacked on the release-workflow PR. Introduce a build-time-only parent POM that centralizes internal module versions and flattens each child's published POM, plus the wiring that depends on it: - root pom.xml: version map (lambda.core/events/serialization.version), managed junit-jupiter, and the flatten-maven-plugin - <parent> blocks in every module POM; internal + junit dependency versions now inherited instead of pinned per module - release.yml: "Record released version" also updates the parent version map; cross-module gate overrides lambda.serialization.version - RELEASING.md documents the version-map update; .gitignore ignores the generated .flattened-pom.xml
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stacked on the release-workflow PR. Introduce a build-time-only parent POM that centralizes internal module versions and flattens each child's published POM, plus the wiring that depends on it:
Issue #, if available:
Description of changes:
Target (OCI, Managed Runtime, both):
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.