[Springframework-developer] JNDI mock move

[Rod J. <rod...@in...>]

I've moved the JNDI mock package from /src to /test. The reason I've done
this is that it's artificially lowering test coverage (this _is_ really test
code), and that I don't think we should encourage people to go down this
route for JNDI testing.  I think the proper way to use Spring is to use it
to help you avoid doing JNDI lookups in your own code. If you do this, you
don't need JNDI mocking: you can just expose bean properties for the
resources that Spring will pull from JNDI.

I'm keen to remove all non-essential code for 1.0 RC1, so I'm using Clover
to help me sniff it out.

I'm also starting a "play" source tree, in which I'm moving some non-core
stuff from /src. I think we should be very focused on what we release in
1.0. And of course paring back to essentials also helps with test coverage.
(Suggestions for a better name than "play" welcome.)

The Visitor stuff from com.interface21.core is on its way to the play tree,
unless there are any objections.

Regards,
Rod

____________________________________________________
Rod Johnson
J2EE Consultant and Author
+44 7973 409 132
rod...@in...

Author of "Expert One-on-One J2EE Design and Development"
(October 2002).
http://www.amazon.com/exec/obidos/tg/detail/-/0764543857/

Founder, Spring Framework:
http://www.springframework.org