Am 25.05.2011 um 10:38 schrieb Anders Hammar:
Well, I do not think it makes sense to add additional manual steps by concept.
You're right. But I see so many advantages to get this in place earlier than
later that I'd argue that yet another manual step is ok. That manual step
should be simple though, not creating a ton of files, logging into several
systems, etc.
Having thought of it, I believe it could be done easily. The only thing we have
to do are the following steps:
a) stage a site somehere into the target directory with a path containing the
${project.version}, eg:
target/
|-- theOtherStuff
`-- versioned-site
|-- 1.0
|-- 1.1
|-- 1.2
`-- index.html
b) have the mentioned index.html in resources redirecting to a subdirectory
${project.version}
c) upload target/versioned-site via wagon to the directory corresponding to the
base-URL of the site.
That should do the trick for now and should (as far as I can see it while
brainstorming) only require some modifications in the pom.xml except for the
index.html in resources. Don't have a clue atm how that could be done more
easily.
To automatically link the older versions, a report plugin has to be written
(I'd like to do that when I "finish" my mail-plugin).
If we want this in the site plugin we should probably work together with the
Apache Maven team.
I don't think this is necessary at all since all can be achieved through a
report plugin and a plugin which calls the report, site:stage and do the upload
via some wagon. Best of all, it does not require any changes to the site plugin
at all.
Kind regards,
Markus
