> I'm not sure it's the best idea, my goal is to move it out of sandbox, > it already has enough experiments > that need completion. and the main goal is to be 'lite' :-). It has a > simple Addon mechanism, and I don't mind > having an optional addon manager impl using OSGI - but I don't want to > get distracted, I started > tomcat-lite experiment >2 years ago. >
Yep, time to stabilize > The first part ( adding manifests to existing tomcat ) seems to have > support so could be done in the trunk. And no consequences outside OSGI world > I don't see any reason for having non-intrusive OSGI support developed > in sandbox - as long > as the code is in a package that is excluded from the official distro, > and is released as a separate > unit it could live in trunk. It'll need the 3 +1 to be released, of > course - but the whole point of > modularity is to be able to develop modules independent of the container. Right > IMO sandbox is for experiments that would replace existing tomcat > components or core stuff. If you do it in > trunk - it's easier to get it released eventually, and you may get > better reviews and attention. Indeed I'll try to spend some time on mavenize tomcatlight first and how it could be done then for tomcat trunk. Next how to OSGIfy the mavenized tomcats, experiences and advices welcomed here --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
