On Jul 6, 2013, at 5:32 PM, Henri Yandell <flame...@gmail.com> wrote: > On Tue, Jul 2, 2013 at 8:43 PM, Jeremy Boynes <jboy...@apache.org> wrote: > On Jul 2, 2013, at 9:41 AM, Henri Yandell <flame...@gmail.com> wrote: >>> >>> I wouldn't expect to deploy the site from tags - a site is a live/current >>> thing. >> >> The core site is a live/current thing, but there is also the >> documentation/reports etc. that would be associated with a specific tag. >> IOW, the site could contain the JavaDoc for 1.1.2, 1.2.0, and 1.2.1 etc. >> That would suggest 1+N parts as Olivier suggests, one for the live site and >> one generated from each tag. >> >> > Fair enough, but why build it from the tag? It's easy enough to use svn cp > to put it in place once and then leave it there rather than keep building > something that shouldn't be changing.
I'm not familiar enough with the mechanics of publishing. I was thinking it would be 1) cut tag (mvn release), 2) build (sub-)site from tagged version, 3) publish (check it in, pubsub does some magic?), 4) never touch it again… I thought it would have to work that way because it's the act of tagging that updates the final version info in the pom. Whereas for the live/current site, every time it's published it overlays itself? --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
