www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ralph Goers (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-4699) Use svnpubsub for all Logging and all of its subprojects
Date Mon, 23 Apr 2012 05:37:55 GMT

    [ https://issues.apache.org/jira/browse/INFRA-4699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13259393#comment-13259393

Ralph Goers commented on INFRA-4699:

Thanks for the link.  The maventest site itself is built with Maven (which I'm not planning
to do) and the site output appears to be destined for the target/site directory.  It isn't
at all clear how it ends up in the CMS svn directory. Under "for each component release" the
doc says "import the generated site to https://svn.apache.org/repos/infra/websites/production/maventest/content/"
which I took to mean it applies to each of the sub projects (the component release), not the
main site, although that doesn't seem to make sense if externals are being used.

I also looked at http://www.apache.org/dev/cmsref.html and checked out the template, but the
skeleton stuff confused me if all I want to do is copy the existing HTML content - do I still
need that? Since maventest doesn't have it I would think not?  I also would like to test it
out somehow before I commit anything to svn but stopped at "install python". I guess my Mac
has both python and Perl installed but my my knowledge of Python is minimal and I've found
that every time I go back to Perl I have to relearn it (I last used it about 7 years ago).
> Use svnpubsub for all Logging and all of its subprojects
> --------------------------------------------------------
>                 Key: INFRA-4699
>                 URL: https://issues.apache.org/jira/browse/INFRA-4699
>             Project: Infrastructure
>          Issue Type: Task
>      Security Level: public(Regular issues) 
>          Components: SvnPubSub, Website
>            Reporter: Ralph Goers
> We would like to have the Logging project site and all of the Logging subproject sites
published via svnpubsub
> Here are the svn urls and the expected website urls: 
> * https://svn.apache.org/repos/asf/logging/site/main/live/ to be deployed at http://logging.apache.org/

> * https://svn.apache.org/repos/asf/logging/site/log4j/live/ to be deployed at http://logging.apache.org/log4j

> * https://svn.apache.org/repos/asf/logging/site/log4j2/live/ to be deployed at http://logging.apache.org/log4j2

> * https://svn.apache.org/repos/asf/logging/site/log4php/live/ to be deployed at http://logging.apache.org/log4php

> * https://svn.apache.org/repos/asf/logging/site/log4cxx/live/ to be deployed at http://logging.apache.org/log4cxx
> * https://svn.apache.org/repos/asf/logging/site/log4net/live/ to be deployed at http://logging.apache.org/log4net
> * https://svn.apache.org/repos/asf/logging/site/chainsaw/live/ to be deployed at http://logging.apache.org/chainsaw

> * https://svn.apache.org/repos/asf/logging/site/companions/live/ to be deployed at http://logging.apache.org/companions

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message