[
https://issues.apache.org/jira/browse/WHIRR-685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13532974#comment-13532974
]
Tom White commented on WHIRR-685:
---------------------------------
No, I think it's fine. I now see where the confusion came about - we don't need
to convert the site to use the Apache CMS, rather we just need to switch to
using svnpubsub to publish our website from SVN. These are the two distinct
options for hosting project websites - see
http://www.apache.org/dev/project-site#intro.
We are still using the existing mechanism for generating the site (Maven site),
and the change I made here is merely to put the website into SVN so that infra
can then set up svnpubsub for us.
Does that make sense?
> Add Whirr website to svn
> ------------------------
>
> Key: WHIRR-685
> URL: https://issues.apache.org/jira/browse/WHIRR-685
> Project: Whirr
> Issue Type: Task
> Components: build, documentation
> Reporter: Tom White
> Assignee: Tom White
> Priority: Critical
> Attachments: Whirr-website-beta-trunk.zip
>
>
> To migrate to svnpubsub we need to have the website checked into svn (note
> that git isn't supported for websites, see
> http://www.apache.org/dev/project-site.html). Currently it is not checked in,
> since we just generate the site with mvn and copy it to a directory on
> people.apache.org. This mechanism will be removed at the end of this month.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
