What I have set up for servicemix is exactly that. The location for the site deployment contains the version number, so that you keep all versions.
http://incubator.apache.org/servicemix/dist/servicemix-3.1-incubating/site/ http://incubator.apache.org/servicemix/dist/servicemix-3.0-incubating/site/ So I actually only launch the "mvn site:deploy" to deploy all the maven site to its own location. Is that what you meant ? On 2/5/07, James Strachan <[EMAIL PROTECTED]> wrote:
On 2/3/07, Guillaume Nodet <[EMAIL PROTECTED]> wrote: > mvn site:site sit:deploy > > It works :-) :) Thanks. I was wondering if we could somehow get that automatically run as part of the release deployment - plus - could we include the version number in the location of where the site goes. i.e. so we can have trunk plus the last few releases' javadoc online. Maybe a simpler approach could be that we just do a 'mvn site:deploy' whenever we are doing a release - so that the online javadoc matches up with the last release. (We can then copy it to some other location manually whenever we do a major release if we wanna keep the old javadoc around). -- James ------- http://radio.weblogs.com/0112098/
-- Cheers, Guillaume Nodet ------------------------ Architect, LogicBlaze (http://www.logicblaze.com/) Blog: http://gnodet.blogspot.com/
