Thanks Andreas for this good point. IMO
-1 for all in jar by default (could be an option ? If yes could be interesting if performance gain), ability to change "in fly" sitemap and xslt is a really good thing (direct effect, no boring compilation wait,...) Any others issues like this will be great help for make the "move to maven" decision. On Fri, 16 Jul 2010 10:51:59 +0200, Andreas Hartmann <andr...@apache.org> wrote: > Hi everybody, > > if there is a consensus to switch to Maven in the 2.1 branch, I'd still > like to address some issues beforehand: > > Should we keep the web application structure? At the moment, files like > XSLT stylesheets etc. are just copied to the webapp directory. With > Maven, a module is usually deployed in a single file, e.g. a JAR file. > > Should we deploy each module in a single JAR file and adjust the > fallback:/ protocol accordingly? Are there any possible performance > implications? > > If we do this, one has to build the JAR file after each change, even to > XSLTs, sitemaps etc. If you use a servlet container that doesn't support > webapp reloading, it is even necessary to restart the servlet container. > > -- Andreas > > > > > Am 15.07.10 18:45, schrieb Rainer Schöpf: >> Florent, Richard, >> >> I'm interested in working on the maven implementation, in case you still >> need >> someone. >> >> Rainer --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lenya.apache.org For additional commands, e-mail: dev-h...@lenya.apache.org
