I'd just like to see what you in Avalon-dev have to say about this:

> -----Original Message-----
> From: Sylvain Wallez [mailto:[EMAIL PROTECTED]] 
> Sent: den 29 januari 2003 21:17
> To: [EMAIL PROTECTED]
> Subject: Re: What is a Parser?
> 
> 
> Vadim Gritsenko wrote:
> 
> > Jeff Turner wrote:
> >
> >> Yes, those deprecation warnings are annoying and 
> misleading, because 
> >> Component is deprecated for Avalon, not Cocoon.  Perhaps Cocoon 
> >> should have a special avalon-framework-nodepr-4.1.3.jar , 
> without the 
> >> @deprecated?
> >
> >
> > My thinking, exactly... I mean, we are going to support Cocoon 2 for
> > some time, without changing basic interfaces like 
> Generator, Action, 
> > etc. And lots of @deprecation in there won't help in raising user's 
> > confidentiality.
> >
> > Avalon gurus out there - should we fork framework? ...
> 
> 
> Answering not to "guru", but to "fork" ;-)
> 
> Yes, all these deprecation warnings are annoying, and furthermore 
> destroy the usefulness of deprecating some classes in Cocoon since we 
> remove all deprecation warnings.
> 
> But instead of forking, what about a tool that automatically 
> removes the 
> deprecation flag on thoses Avalon classes that aren't considered 
> deprecated in Cocoon ?
> 
> A small BCEL-based tool could easily do the trick, and would be used 
> before committing a new version of Avalon jars in Cocoon's CVS.
> 
> Thoughts ?
> 
> Sylvain

It seems like the @deprecation of ComponentManager etc. is annoying
some people to a fairly large extent.

I was thinking... Could we remove the @deprecated tags from the classes 
in question and just leave it with a note in the JavaDocs saying that 
the service.* package is much much better and that you should use it
instead unless you have a reason not to?

As I understand it, every container must support ComponentManager,
Composable, etc. anyway... At least until Avalon 5.

/LS


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to