Re: [Springframework-developer] Removing cyclic dependencies in sub-packages

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

>Strictly speaking, the AopUtils move is not backward-
compatible, but I'm not keen on keeping a deprecated class in 
the old place. As we're talking about an internal class here, 
I guess this won't break any existing application. This 
raises the following issue: What exactly constitutes our 
public API? We will occasionally face the need to revise 
internals, even for point releases...

I'm happy with this move. The only legitimate reason people 
might use it is to check whether a particular instance is an 
AOP proxy in a test case (rather than application code).

I think we should publish a list of the public API contracts 
that won't change. With the AOP stuff, I've made some of the 
classes package-visible, but that's often impossible.

Axis did this way back and I thought it was a good idea. 

Regards,
Rod