Repository navigation
Use Impl suffixes for concrete framework implementations - #49
Merged
Merged
Conversation
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.
Concrete framework implementations use inconsistent class names, including adapters and inherited behavior implementations outside
implpackages. This applies the requestedImplsuffix to 309 implementation classes and updates constructors, imports, SPI registrations and necessary Java documentation references.The change preserves 45 component bean IDs and 19 DSL node identifiers. It also maps 270 intentional Java source-file renames while continuing to verify the original imported Git trees and references. Two broker-free Spring tests exercise the original RabbitMQ component names and qualifier wiring.
Concrete implementation FQNs change, so this is source- and binary-breaking for callers that reference those classes. Interfaces, configuration/data types and generated SDKs are not arbitrarily renamed. All POMs retain the existing 26.10.23 source model; no immutable 26.10.23 artifact is replaced. Rollout requires a separately reviewed whole-framework CalVer release and consumer alignment. No merge, release or adoption is implied by this source checkpoint.
Validation:
eadf7d59f357d41a5300e1ea2162b2fdab2eb576: 5,474 reported tests, 5,450 passed, 0 failures/errors, 24 skips. Both new RabbitMQ tests passed; the total includes 18 passing maintained standalone examples.54c4282c20f4cca9565cb3201962c713099fd2f639c0f88af27d7b23a19cb6a6.Required checks and CodeQL for this PR must complete before merge; release and consumer planning are separate gates.