Re: [PROPOSAL] Avalon Components

> Ok, here is how I thought we could do Avalon Components:
> 
>  1   - rename jakarta-avalon-excalibur CVS module to avalon-components
>  1-b - symlink so that you can checkout it as jakarta-avalon-excalibur
>        for some time
>  2   - move the cornerstone component dirs under that repo (simple cp)
>  3   - add them in the "excalibur" build
> 
> This would make us almost instantly have a common repo for all 
> components that we can open to the James committers as you say.
> 
> The only real work would be to add them to the build of "excalibur", 
> which is not a big feat.
> 
> This would be a first step; in the meantime we can still migrate package 
> per package of non-Avalon stuff to JC, and decide about the others as we 
> proceed. But in the meantime this would mean that we have taken a step 
> towards a single component system, and towards a tighter relationship 
> with our users.
> 
> Deal?

+0 (ie yes but I have different priorities :)

cheers,

- Leo