On Fri, 16 Jul 2010, Andreas Hartmann 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.
That's the default, but there is no reason why it has to be so. More precisely, this the default goal of the package phase of the default lifecycle if you specify jar packaging in the toplevel pom.xml file. For lenya, war packaging is probably the right thing. The prepare-package phase corresponds to the (current) ant target "webapp", and the package phase to the ant target "war". If you don't want the .war file to be built, either stop the build process after the prepare-package phase or create a custom packaging type. > 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. There is no need to do this. It may need a bit of work to get the maven configuration right, but it's all configurable. Rainer --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lenya.apache.org For additional commands, e-mail: dev-h...@lenya.apache.org
