+1 as long as each project can be done separately (ie each plugin and the main site). Making it an artifact would be great to do so we can offer a download of the maven docs in a standard way.
This does need to be considered along with the other discussion that I haven't had a chance to pull together yet, about what is actually displayed on the front maven site and what is historical. I think the conclusion was that the site should be the same across releases with the exception of news and status, FAQ and other things unrelated to the actual release. - Brett > -----Original Message----- > From: Vincent Massol [mailto:[EMAIL PROTECTED] > Sent: Thursday, 4 September 2003 6:36 PM > To: [EMAIL PROTECTED] > Cc: 'Maven Developers List' > Subject: Several web site versions in CVS > > > Hi dIon, > > I've looked at the new strategy for rendering several > websites for the plugins (by storing the different versions > in CVS). I think it can be improved... :-) > > Here are my ideas: > > - I don't think it's normal to store history data in CVS. A > SCM is meant to do that for you. I won't save several > versions of the same file so why would I do this for web sites. > > - A website is a production (a.k.a artifact) of a project and > as such it should go in the local/remote repository. Maybe > under a new "webs" or "websites" type? > > - The different versions of the websites should be stored on > the web server. > > - It should be possible to reinstall a web site by having a > "site:redeploy" goal that takes as input a website version. > That would fetch the website from the local/remote repo and > redeploy it. > > What do you think? > > Thanks > -Vincent > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
