Eliminate warnings in SPR-0000 template project
Add convenience script for creating repro projects

    ./create-repro-project.sh SPR-9876

will create a new project based on the default SPR-0000 template

    ./create-repro-project.sh SPR-0000-war-xml SPR-9878

will create a new project based on the SPR-0000-war-xml template

In any case, only the pom.xml file and contents of 'src' directory are
copied into the new project, avoiding any inadvertent copying of
'target' directory, eclipse metadata or other transient files.

Finally, the newly copied pom.xml is processed to replace the
original artifactId with that of the new project directory name.

After this script is run, the new project directory should be directly
importable into Eclipse/STS/IDEA as an existing Maven project.
Attempt (unsucessfully) to reproduce SPR-8651
Prove inability to reproduce SPR-8663
not passing test
Merge pull request #5 from marcin-lukasiuk/master

update to SPR-8639
ADD PROJECT FOR SPR-8661
Added test cases for SPR-8683
Merge pull request #6 from dsyer/SPR-8683

Added test cases for SPR-8683
Simplify and demonstrate workaround for SPR-8639

As originally submitted, SPR-8639 used ProxyFactoryBean to apply
MyInterceptor to beans A, B and C.

Typically this works fine, but because of a subtle circular dependency
being introduced due to A and B depending on C and C needing to autowire
D, the PFBs for A and B are prematurely queried for their type (to see
if they are autowire candidates for C) and this trigger a
BeanAlreadyInCreation exception that is subsequently suppressed.

This is a very specific use case and highly unlikely to be reproduced
by other users with any frequency.  However, we will address it even if
only by allowing the original exception to propagate fully.

In the meantime, I have refactored the test case to demonstrate use of
BeanNameAutoProxyCreator in lieu of the original ProxyFactoryBean, and
this approach is better in every way: it is more concise, more readable,
requires fewer bean definitions, and best of all does not suffer from
the above-mentioned bug.

Issue: SPR-8639
Reproduce SPR-8639 failure in anticipation of fix

This change re-introduces ProxyFactoryBean usage to demonstrate the
issue described in the previous commit.  Notice that debug logging is
enabled.  The following log statement documents 'ignoring' (suppressing)
the underlying exception.

To fix this issue, we'll see about allowing this exception to propagate
when dealing with ProxyFactoryBeans that do not have a fixed object type
that can be determined by static generics analysis or a call to
getObjectType on an early FactoryBean reference.

DEBUG: org.springframework.beans.factory.support.DefaultListableBeanFactory
- Ignoring bean creation exception on FactoryBean type check:
org.springframework.beans.factory.BeanCreationException: Error creating
bean with name 'b' defined in class path resource
[org/springframework/issues/ReproTests-context.xml]: Cannot create inner
bean 'org.springframework.issues.B#7e9ffe3f' of type
[org.springframework.issues.B] while setting bean property 'target';
nested exception is org.springframework.beans.factory.BeanCreationException:
Error creating bean with name 'org.springframework.issues.B#7e9ffe3f'
defined in class path resource
[org/springframework/issues/ReproTests-context.xml]: Cannot resolve
reference to bean 'c' while setting bean property 'c'; nested exception
is org.springframework.beans.factory.BeanCurrentlyInCreationException:
Error creating bean with name 'c':
org.springframework.beans.factory.FactoryBeanNotInitializedException:
Cannot determine target class for proxy

Issue: SPR-8639
Add project for SPR-8725
SPR-8714 repro project
Add repro project for SPR-8711
Merge pull request #7 from srgrodeon/master

Test case for rest template 404
Add missing @ResponseBody to controller method
Add test cases to SPR-8714
SPR-8769
SPR-8769
"Add repro project for SPR-8813"