Hi Erik,

Btw, we really need to change the deployment for the website from Maven scp to a SVN checkout - this is a) a infra requirement [1] and b) will make sure that those things don't happen. The only downside is that we need to keep a copy of the generated stuff in SVN but that was discussed to length already and we don't really need to re-hash that.
...
[1] http://www.apache.org/dev/project-site.html

Any other opinions and/or takers for that?

In due time, I am willing to take care of a part of that.
Due time means not February, _maybe_ March. The part I would
take care of is deploying the main and component level site
via SVN.
I will not waste time with deploying the module level site
via SVN. Whenever we rename or move a class, we would have
to manually update the SVN contents of the generated JavaDocs
and cross-referenced sources to get rid of the old artifact.
To make matters worse, the cross-referenced sources need
different SVN keywords so the source values are not replaced.
I'd rather remove the module-level site than try to maintain
the generated information in SVN.

For the legacy site, I don't have a problem with that. The code
is not changing much anymore, so it remains a one-time effort.
But IIRC, Maven 1 has poor staging support. Maybe I'll have to
use Maven deployment to localhost and a few symbolic links to
get the pages into a subversion controlled directory.

You mentioned the possibility of running nightly builds directly
on people.apache.org. Could and should we use that to generate
the module-level subsites on a weekly or even daily basis there?
Then we don't have to deploy those at all.

cheers,
  Roland


I'm a bit limited re generating all the sites since I don't have all the deps installed (namely Maven1) but I'm happy to do the checkout on people.a.o as soon as we have all the stuff in SVN...

Cheers,
Erik


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to