I'm OK with this, but I'm not sure if infra is OK with that structure. Based on that I think what we want to request is the following be added to the rules.
/x1/www/www.apache.org/dist/logging: %(DIST)s/release/logging /x1/www/logging.apache.org: %(ASF)s/logging/site/main /x1/www/logging.apache.org/log4j: %(ASF)s/logging/site/log4j /x1/www/logging.apache.org/log4j2: %(ASF)s/logging/site/log4j2 /x1/www/logging.apache.org/log4php: %(ASF)s/logging/site/log4php /x1/www/logging.apache.org/log4cxx: %(ASF)s/logging/site/log4cxx /x1/www/logging.apache.org/log4net: %(ASF)s/logging/site/log4net chainsaw and log4j companions also show up on the main site. Do we also want those? Ralph On Apr 16, 2012, at 12:37 AM, Christian Grobmeier wrote: > On Mon, Apr 16, 2012 at 9:31 AM, Ralph Goers <[email protected]> > wrote: >> I'm actually more concerned with us having to use svnpubsub >> (see http://www.apache.org/dev/project-site.html). The maven team created a >> plugin - http://maven.apache.org/sandbox/plugins/asf-svnpubsub-plugin/ to >> aid in this but I haven't tired it. I also understand that it requires the >> main website to have something done to it first. > > didn't know about the mvn plug - thanks! > >> Log4j2 uses the Maven site plugin so I guess I really need to know is what >> the location of the svn directory would be to pass to svnpubsub:prepare. > > What about: > http://svn.apache.org/repos/asf/logging/site/pubsub/$project > > For example: > http://svn.apache.org/repos/asf/logging/site/pubsub/log4j2 > http://svn.apache.org/repos/asf/logging/site/pubsub/log4php > http://svn.apache.org/repos/asf/logging/site/pubsub/main (start site) > > and so on > > > > >> >> Ralph >> >> >> On Apr 16, 2012, at 12:14 AM, Christian Grobmeier wrote: >> >> On Mon, Apr 16, 2012 at 6:38 AM, Ralph Goers <[email protected]> >> wrote: >> >> Do we have a process in place for updating the web site? I'm trying to go >> through any issues that might exist with doing a release of Log4j2 and this >> is one of them. >> >> >> I am not aware of a specific process (old timers might want to correct me). >> So far I know we have updated the website whenever the release has >> been published. I am not a huge fan of restricting website updates to >> releases and think we should be able to update at any time we want. >> >> This again touches the question with pubsub. We need to make a >> decision if we move to mvn site:deploy or do something else. >> >> Cheers >> Christian >> >> >> -- >> http://www.grobmeier.de >> https://www.timeandbill.de >> >> > > > > -- > http://www.grobmeier.de > https://www.timeandbill.de
