Re: Mandatory svnpubsub migration by Jan 2013

On Fri, Feb 24, 2012 at 10:01 AM, Ralph Goers <[email protected]> wrote:
> The log4j and log4net sites both have the powered by Maven logo on them so I expect they are also built with Maven.
>
> If you look at /x1/www/logging.apache.org on people it isn't owned by the proper user so we aren't being managed by this process yet.

That was always a problem in the past. I hope we would get rid of this
with pubsub

>
> What is wrong with having multiple entries in the config like ant does?

Not sure, but we would have nested directories. I thought it would be
easier  to make an update in one go?

Ant config:
/x1/www/ant.apache.org: %(ASF)s/ant/site/ant/production
/x1/www/ant.apache.org/ivy: %(ASF)s/ant/site/ivy/production
/x1/www/ant.apache.org/ivy/ivyde: %(ASF)s/ant/site/ivyde/production

Logging config would be like that:
/x1/www/logging.apache.org: %(ASF)s/logging/site/trunk/docs/
/x1/www/logging.apache.org/log4php %(ASF)s/logging/site/trunk/docs/log4php

I do not know, but my guess is we would need to separate the
directories for the different sites in svn, like:

/x1/www/logging.apache.org/: %(ASF)s/logging/site/main/trunk/docs/
/x1/www/logging.apache.org/log4php: %(ASF)s/logging/site/log4php/trunk/docs/

Or is pubsub supposed to work with nested directories of that kind?

Cheers
Christian