Bringing this up again, as it needs to be resolved. "Vincent Massol" <[EMAIL PROTECTED]> wrote on 04/09/2003 06:36:22 PM:
> 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. So that users with old versions can go look up the old documentation, e.g. in Maven's case, beta 10 users can look at the install docs and we can update them for 1.0-rc1 as we go. > - 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? This is a great idea, but doesn't the 'dist' goal already include the site? If not, why not? Also, there is a site:war goal too, so the site can easily be deployed in a web server. > - The different versions of the websites should be stored on the web > server. Cool. > - 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. Ok. -- dIon Gillard, Multitask Consulting Blog: http://blogs.codehaus.org/people/dion/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
