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 |
*-----------------------------------------------------*
