For the main site, I worked with Joe: he incorporated site conventions to the CMS web UI to offert online editing and publishing
Then extpaths.txt was added to let components sites published with svnpubsub You have half of the story, I have the other one in site branch :) Envoyé depuis mon mobile ----- Reply message ----- De : "Benson Margulies" <bimargul...@gmail.com> Pour : "Maven Developers List" <dev@maven.apache.org>, "Joe Schaefer" <joe_schae...@yahoo.com> Objet : Maven site & svnpubsub Date : sam., févr. 25, 2012 20:35 I've got my first offering in this department working, at least a little. org.apache.maven.plugins:asf-svnpubsub-plugin is a Maven plugin that published an entire site to a subversion tree. It has no CMS integration. Once this item is under control, I plan to pick up the trail of breadcrumbs that Joe left me to fit mvn site content into the CMS's control structure. I've site-deployed the doc such as I have it to maven.apache.org/sandbox/plugins/asf-svnpubsub-plugin. Source is https://svn.apache.org/repos/asf/maven/sandbox/trunk/plugins/asf-svnpubsub-plugin. The intent here is that complex sites, such as the main maven site, can be handled by judicious use of 'excludes'. However, since the SCM provider API has the 'simple' form of includes and excludes (only one of each), I have some qualms as to whether it will really work for the top-level site. I'm very much in one-thing-at-a-time mode; this much should at least be useful for 'leaves'. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
