Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support non-public BeanOverrideProcessor implementations in the TestContext framework #32485

Closed
sbrannen opened this issue Mar 18, 2024 · 0 comments
Assignees
Labels
in: test Issues in the test module type: task A general task
Milestone

Comments

@sbrannen
Copy link
Member

Overview

A BeanOverrideProcessor will typically only be referenced via @BeanOverride(MyCustomProcessor.class) which is used as a meta-annotation on a user's/project's custom composed annotation (analogous to @TestBean and @MockitoBean).

In light of that, there's seldom a reason to make such a type public.

In order to allow users to make BeanOverrideProcessor implementations package-private, we should ensure that BeanOverrideParser is able to instantiate non-public BeanOverrideParser types.

We should also investigate whether TestBeanOverrideProcessor and MockitoBeanOverrideProcessor need to be public.

Related Issues

@sbrannen sbrannen added in: test Issues in the test module type: task A general task labels Mar 18, 2024
@sbrannen sbrannen added this to the 6.2.0-M2 milestone Mar 18, 2024
@sbrannen sbrannen self-assigned this Mar 18, 2024
@jhoeller jhoeller modified the milestones: 6.2.0-M2, 6.2.0-M1 Mar 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: test Issues in the test module type: task A general task
Projects
None yet
Development

No branches or pull requests

2 participants