You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Joe Schaefer (Closed) (JIRA)" <ji...@apache.org> on 2012/03/06 04:02:14 UTC
[jira] [Closed] (INFRA-4466) please create a maventest.a.o CMS
sandbox
[ https://issues.apache.org/jira/browse/INFRA-4466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joe Schaefer closed INFRA-4466.
-------------------------------
Resolution: Fixed
Infra's work is done here AFAICT.
> please create a maventest.a.o CMS sandbox
> -----------------------------------------
>
> Key: INFRA-4466
> URL: https://issues.apache.org/jira/browse/INFRA-4466
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: CMS
> Reporter: Hervé Boutemy
>
> as discussed on infrastructure@a.o:
> can you create a CMS sandbox for http://svn.apache.org/repos/asf/maven/site/trunk ?
> let's call it maventest.apache.org, for example, or whatever is ok for you
> the command to generate the site is "mvn site", and the generated HTML content is in target/site.
> Each time the svn content is modified, the CMS should build and publish the site.
> The corresponding site would actually contain 241 files in 59 directories for 5.6MB.
> Then I could try to add to this TLP site some components' sites, like /ant-tasks/ for example, using this REST api
> This would IMHO perfectly the misc workflows we actually use to modify maven.a.o site, with only minor changes in the publish commands: no more scp.
--
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