commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From robert burrell donkin <>
Subject Re: Query: Hosting Avalon Components
Date Mon, 28 Apr 2003 20:40:35 GMT
the charter says:

"2. The package library is not a framework but a collection of components 
designed to be used independently."

this clause makes it very hard to see how avalon components could be 
accepted into the jakarta-commons proper. (this isn't the same thing as 
banning all dependencies on avalon.)

of course, if amendments to the charter are on the agenda then anything's 
possible. i can actually understand some of the arguments for wanting a 
repository for avalon components within the jakarta-commons structure. 
there's a certain synergy between component-oriented development whether 
with avalon or without. if the energy is there from the avalon component 
developers then maybe jakarta-commons could host a jakarta-commons-avalon 
repository for tightly scoped, commons-style avalon components.

- robert

On Thursday, April 24, 2003, at 09:26 PM, Berin Loritsch wrote:

> It is my understanding that Jakarta Commons won't host Avalon components
> because they are not general purpose code.  IOW, using them outside the
> context of an Avalon container doesn't really make sense.
> I want to confirm if my understanding is correct.  If not, under what
> circumstances would that be viable.  A developer on that list thinks
> that the general attitude for hosting Avalon components vs. utility
> code has changed for this project.
> Is there any truth to that?
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message