Package issues

Interface Summary

Sjc69Tests.MyBean

Class Summary

Sjc17Tests	SJC-17 demonstrates the fact that JavaConfig's approach to programmatic bean creation is fundamentally incompatible with RequiredAnnotationBeanPostProcessor.
Sjc54Tests	SJC-54 came up because of an intentional break in backward compatibility from 1.0M2 to 1.0M3.
Sjc55Tests	SJC-55 proposes an improved programming model for configuring aspects with JavaConfig.
Sjc55Tests.MyAspect
Sjc56Tests	SJC-54 revealed a bug wherein abstract Configurations would not be processed unless they have at least one public Bean method.
Sjc57Tests	SJC-57 revealed a bug where Reusable aspects (@Aspect-annotated
Sjc57Tests.StandaloneAppConfig
Sjc60Tests	SJC-60 exposed a bug with JavaConfig calling refresh() multiple times in the hierarchical context situation below.
Sjc60Tests.ApplicationConfiguration
Sjc60Tests.ApplicationConfiguration2
Sjc69Tests	SJC-69 revaled a bug in the way addConfigClass() works with regard to bean overrides.
Sjc69Tests.MyBeanA
Sjc69Tests.MyBeanB
Sjc69Tests.MyConfigA
Sjc69Tests.MyConfigB
Sjc69Tests.MySpringContext
Sjc70Tests	SJC-70 revealed the fact that AutoBean methods do not execute their method body if present.
Sjc91Tests	SJC-91 deals with a compatibility issue between JavaConfig and Spring Core - checking @Required annotations.