Hi,
Can be easy :-)
mvn site site:stage and all the content of all modules will be in
${project.build.directory}/staging (target/staging).
But to achieve this and having something easy we must the site module
on the top!
Means here http://svn.apache.org/repos/asf/tomcat/taglibs/trunks/
As we don't release the site (that doesn't shok me :-) ).
With this tree deploying the site will be as easy as: mvn clean site
site:stage && mvn scm-publish:publish-scmMake sense ? I can work on that or help you if you want. 2013/6/24 Henri Yandell <flame...@gmail.com>: > FYI that I'm digging into the Taglibs site to figure out how it is we go > from 15 Maven target/site directories to 1 site. > > I'm then going to write a dumb shell script that copies the relevant parts > to a Tomcat site/taglibs checkout, allowing for the site to be updated. I'm > sure there's a very clever Maven plugin that can take care of this and > handle the logic of the 15 maven projects becoming 1 site, but I'd rather > build Lego :) > > Hen -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
