avalon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Neeme Praks <ne...@apache.org>
Subject Re: avalon-commons
Date Sat, 26 Apr 2003 09:33:28 GMT

Peter Donald wrote:

>On Sat, 26 Apr 2003 02:03, Berin Loritsch wrote:
>  
>
>>They were more supportive of opening up an "Avalon Commons" of sorts.
>>    
>>
>I didn't get that. Actually I got quite the opposite - it was you who seemed 
>to be pushing for that.
>  
>
As I see it, the results from that "Query: Hosting Avalon Components" 
thread are:
* if some commons component has an avalon wrapper, keep it in commons, 
together with the project
* having only a wrapper hosted at commons (without the actual project 
code) is not desirable. rather, these wrappers should be in avalon-commons
* all such cases should be considered case-by-case, but the general 
feeling is towards avalon-commons, unless the project is already in 
jakarta-commons

For me personally, the impression from that discussion is, that nobody 
is really objecting to having wrapper code in jakarta-commons (this will 
be anyway handled case-by-case) but the recommended direction is towards 
avalon-commons.

Some references:
http://article.gmane.org/gmane.comp.jakarta.commons.devel/22864
http://article.gmane.org/gmane.comp.jakarta.commons.devel/22873
http://article.gmane.org/gmane.comp.jakarta.commons.devel/22813
http://article.gmane.org/gmane.comp.jakarta.commons.devel/22823

Just trying to keep the discussion above the emotional level...

Rgds,
Neeme


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org


Mime
View raw message