Ulrich, > > With respect to the former, I think sevak api should go to say incubator. The >catalina impl > > should either go with it, or end up with Catalina (as a separate download?). > > I think the Sevak API should remain with Phoenix, because it is a > central feature to an application server, much like JMX. Since Sevak is > usable with Merlin as well, it might also be conceivable to move it to > Excalibur.
It goes without saying that it should work with Phoenix, Merlin and the replacement. Excalibur is plain wrong for this. > > The is also merit to having the Jo and Jetty Sevak impls together in the same (new) > SourceForge > > project. > > I'm not sure what licensing issues could conceivably exist with the > implementations. Sevak is just using the public APIs of 3rd party > products. Surely there can't be any licensing issues with using public APIs? Sevak API is fine. The impls, clearly, import other people's codebases. "using public APIs" also counts GPL. Here we are only talking about LGPL and a proprietary credit-affording license for Jetty. > The JARs don't have to be in Apache's CVS, they could be extra > downloads. I'm all for making it as easy as possible for users. We have had instruction on 'import'. Jars here or there are irrelvant. - Paul __________________________________________________ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
