Container, jasper and build are a good start. I think connectors should be included too.
Servletapi is obviously different, and even in the current build it's downloaded as a jar AFAIK. You can still have separate releases and release cycles for different components - even if they reside in the same SVN tree ( or even same java/ source tree ). As we learned, labels are cheap, so there's no problem if you release and label different things. I hope more components could follow the 'separate release' model - /admin and most webapps, many other things that could be modules. At least in 6.x timeframe. Costin On 11/22/05, Yoav Shapira <[EMAIL PROTECTED]> wrote: > Hi, > I also think a re-org into a single codebase for build, container, > jasper is in order. Connectors and servletapi are a bit different > because they have their own releases (and release cycles). I think > from the users' perspective, a single SVN repository is cleaner and > makes building easier. > > Yoav > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
