Skip to content

Refine AOT Repositories infrastructure #3267

@mp911de

Description

@mp911de

Revise our AOT API surface as many methods have only a single usage within Commons and are not worth to be exposed. We also should reduce mutability and clarify the contracts for a clearer structuring of AOT contributions. Right now, parts are here and there. Introducing a AotRepositoryContextSupport for delegation to AotContext seems to be a good way to shield implementations from dropping future methods. Also, RepositoryRegistrationAotContribution and RepositoryRegistrationAotProcessor are super entangled and it makes sense to split both for a cleaner design.

Metadata

Metadata

Assignees

No one assigned

    Labels

    has: breaking-changeAn issue that is associated with a breaking change.theme: aotAn issue related to Ahead-Of-Time processingtype: enhancementA general enhancement

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions