My feeling is that we need to do (3) to energize (1) and (2) (or (4) -
The
Gathering). I also feel we need to something both useful and manageable
for (3) that can serve as a baseline example for future work.
My actual suggestion would be to start with the XML Configuration
component, along with the Testing Suite, supported by a site
infrastructure designed to scale to multiple components.
Testing seems to be a hot button right now all over Jakarta. But we
would also need something to test. The XML Configuration component
saw the largest number of votes. Merging the Avalon and Struts
components seems manageable, and may provide a lot of
utility to other products.
Peter Donald wrote:
>
> Hi,
>
> As the process seems to have slowed and every one seems to be talking about
> different approach maybe we should look at exactly what we want. There is
> three different things that people are talking about
>
> 1. component repository (ie ToolForge+CJAN)
> 2. vetted/tested/approved components (ie Avalon+CJAN)
> 3. base util (Something similar to AUT - Apache Utility Toolkit).
>
> I am happy to work on (3) and are familiar enough with both Turbine and
> Avalon bases that I could help extract the code from them that was
> necessary. I already work on (2) ;)
>
> So if there is enough supporters from other projects do you think it would
> be useful to start AUT now using the standard apache model? For (1) I think
> there needs to be a few issues resolved. Thoughts?
>
> Another model no one has mentioned is the "gatherer" style. ie Code remains
> in whatever CVS it is in now but there is another process to gather
> components from all the different places and publishes them?
>
> So you would have an XML descriptor for each project that lists all
> sub-products. So if you wanted digester from struts, the connection pool
> from turbine and the feedReader from jetspeed you just write your own
> script. This script would indicate your dependencies. During build these
> dependencies are sucked from CJAN/whatever and placed in lib directory. In
> many ways this can draw on and complement gump. Thoughts?
>
> Cheers,
>
> Pete
>
> *-----------------------------------------------------*
> | "Faced with the choice between changing one's mind, |
> | and proving that there is no need to do so - almost |
> | everyone gets busy on the proof." |
> | - John Kenneth Galbraith |
> *-----------------------------------------------------*
