Minimized ASM usage
In particular, avoid accidental usage of ASM for core JDK types - which will fail in case of a new bytecode version in the JDK, even if the application itself has been compiled with an earlier bytecode target. Issue: SPR-10292
This commit is contained in:
@@ -79,7 +79,7 @@ public class ImportedConfigurationClassEnhancementTests {
|
||||
|
||||
|
||||
@Test(expected=BeanDefinitionParsingException.class)
|
||||
public void importingAnNonConfigurationClassCausesIllegalArgumentException() {
|
||||
public void importingNonConfigurationClassCausesBeanDefinitionParsingException() {
|
||||
new AnnotationConfigApplicationContext(ConfigThatImportsNonConfigClass.class);
|
||||
}
|
||||
}
|
||||
@@ -103,5 +103,5 @@ class ConfigThatDoesImport extends Config { }
|
||||
class ConfigThatDoesNotImport extends Config { }
|
||||
|
||||
@Configuration
|
||||
@Import(Void.class)
|
||||
@Import(TestBean.class)
|
||||
class ConfigThatImportsNonConfigClass { }
|
||||
Reference in New Issue
Block a user