Leo Sutic wrote:
Berin,
I'm sure that solves the problem of how to get rid of the Component
interface, but the problem the Cocoon people are having is this:
If anyone has written any code for Cocoon, they get
deprecation warnings.
This makes Cocoon API seem unstable.
That is partly because they extend/use the Cocoon declared components
(Action, Generator, etc.) which in turn extend Component. If they
no longer extend Component, then there are no deprecation warnings,
and everything still works.
It doesn't matter whether there is an upgrade path, or if it
is a real simple one - it is about percieved stability.
I'm fine with your change to package.html - go ahead and commit it.
But, could you post the same thing to cocoon-dev and see if
it solves their problem?
Ok.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
