Add SPR-10297 repro project in initial state
Add Gradle eclipse plugin
Confirm that moving load-time-weaver works around stackoverflow
Revert "Confirm that moving load-time-weaver works around stackoverflow"

This reverts commit 9306f5517c28d6b6387171366787f194b0ee3dd8.
Fix inherent cyclic dependency

 - Per beans.xml, Person is injected with a reference to a PersonService.

 - Per aop.xml, use of @Configurable, and inclusion of aspectj-autoproxy
   and load-time-weaver in beans.xml, instances of Person created using
   'new' will have dependency injection managed by Spring per the
   instructions in beans.xml

 - a PersonService bean is also declared in beans.xml

 - the constructor for PersonService creates a `new Person()` object

 - therefore, Spring tries to create a PersonService object, which
   itself tries to create a Person, which needs a PersonService in
   order to fulfill its dependency injection needs.

This is a fundamental cyclic dependency, and one that as far as I can
see cannot be broken without changing the relationship between
PersonService and Person.

For example, why must PersonService create a new Person in its
constructor? If it instantiated Person objects via 'new' at any later
point, the cycle would be broken.

This commit demonstrates breaking the cycle by simply commenting out
the `new Person` statement from the PersonService constructor.
Merge branch 'SPR-10297' into master