You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4php-dev@logging.apache.org by "Christian Grobmeier (JIRA)" <ji...@apache.org> on 2010/05/06 08:05:48 UTC
[jira] Resolved: (LOG4PHP-107) Site should updated via svn
[ https://issues.apache.org/jira/browse/LOG4PHP-107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christian Grobmeier resolved LOG4PHP-107.
-----------------------------------------
Resolution: Fixed
mvn site-deploy creates a new folder in the target folder which can be committed with:
svn commit -m 'your message'
Then please follow this:
ssh -l username people.apache.org
cd /www/logging.apache.org/log4php
svn update
After a while the site is mirrored.
Attention: some huge commits might fail if tlsext is compiled into your svn client.
> Site should updated via svn
> ---------------------------
>
> Key: LOG4PHP-107
> URL: https://issues.apache.org/jira/browse/LOG4PHP-107
> Project: Log4php
> Issue Type: Task
> Components: Website
> Affects Versions: 2.0
> Reporter: Christian Grobmeier
> Assignee: Christian Grobmeier
> Fix For: 2.1
>
>
> Currently logging uses mvn site site-deploy to commit the generated page into svn. On the webserver they do svn update. We have been asked to follow this process too
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.