You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ImportsContextCustomizer currently creates an infrastructure that requires a reference to a test Class but it turns out that only the FQN of the test class is required.
We can relax this private arrangement to only use the name. A side effect of that is that it would prevent spring-projects/spring-framework#29168 from happening.
The text was updated successfully, but these errors were encountered:
snicoll
changed the title
Relax ImportsContextCustomizer to rely only a test class name
Relax ImportsContextCustomizer to rely only on a test class name
Sep 19, 2022
If we decided to not include ImportsContextCustomizer at runtime, then no bean definition would be contributed and that would make this issue irrelevant. However, given that the runtime effectively only need a class name, it makes sense to change this regardless.
ImportsContextCustomizer
currently creates an infrastructure that requires a reference to a testClass
but it turns out that only the FQN of the test class is required.We can relax this private arrangement to only use the name. A side effect of that is that it would prevent spring-projects/spring-framework#29168 from happening.
The text was updated successfully, but these errors were encountered: