I sent some detailed concerns about jetty modules that included same issues that Gary pointed out along with some other stuff (i.e. transparency). I thought Taylor was going to follow up with the Jetty team.
regards, Eugene PS: Fernando, you may as well just run Jetty as a main class or start it from their maven plugin. Steven Harris wrote: > Would be great to merge them. Would require coordination with the > jetty folks though. > > On Nov 7, 2007, at 7:34 PM, Gary Keim wrote: > >> I’ve been experimenting with Jetty/Terracotta/Eclipse as a way to >> easily develop TC-enabled webapps. It seems very promising… might >> even have to throw Maven in there too. >> >> There are two different Jetty integration modules, one for general >> DSO support, which ships with the TC kit, and one for session >> clustering, which is housed at svn.codehaus.org/jetty. The latter >> module is not update-to-date with the TC 2.5 release that’s in the >> works. Wouldn’t it be better to consolidate these into a single >> module that would live on the TC forge (and use Maven) so it would be >> easier to keep it updated? This is especially important since we >> have chosen to not support module version ranges, so each new TC >> version will require separate module branches to match. >> _______________________________________________ tc-dev mailing list [email protected] http://lists.terracotta.org/mailman/listinfo/tc-dev
