Am 25.05.2011 um 06:53 schrieb Anders Hammar: I see lots of benefits of deploying each version of the site to a different location. However, when you say symlink, do do you mean file system symbolic link? Wouldn't that mean that we need to keep the versioned site deployment in different folder tree than the latest one? That could make some other web server configuration more cumbersome (need to add aliases possibly).
I'll dive into that topic later that day. I have a few Ideas of how to achieve what you want and will have a look on how to do it. I think it would great if http://mojo.codehaus.org/awesome-maven-plugin/ would take me to the latest (official) site of this plugin. If I want to view a specific version of the site, I'd just add the version (or similar) number: http://mojo.codehaus.org/buildnumber-maven-plugin/1.0/ That should not be too much of a problem in general. But as always, the details deal the pain. An automatic solution would be good, but I don't see a problem with having a manual step. Hey, there are lots of manual steps in the release process already. Well, I do not think it makes sense to add additional manual steps by concept. How about extending the site:deploy goal? It should not be too difficult to add the ${project.version} as a directory to the path the site gets deployed to. What would be missing is an index.html which simply redirects to the current version using http headers. But the generation of said index.html should be trivial. I do not think that symlinking is a way to get to the current version. Both because following symlinks isn't necessarily allowed on a given target server and symlinking simply does not work on any operating system. What troubles me at the moment is how to link from the current version to the older versions. Maybe this could be done via a special report plugin? What would be left is a) extending the site plugin with a special goal like site:deploy-versioned and b) a report plugin which examines the deployment site and adds the older versions to the site. Probably a) and b) could be combined to a new plugin? Kind regards, Markus
