You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@empire-db.apache.org by "Jörg Reiher (JIRA)" <em...@incubator.apache.org> on 2009/06/27 14:14:47 UTC
[jira] Resolved: (EMPIREDB-39) Update project website
[ https://issues.apache.org/jira/browse/EMPIREDB-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jörg Reiher resolved EMPIREDB-39.
---------------------------------
Resolution: Fixed
Assignee: Jörg Reiher (was: Rainer Döbele)
updated...
just had to login via ssh to "people.apache.org", changed to directory "/www/incubator.apache.org/empire-db/"
(that is where our web site is located) and called "svn update"; because it works as follows:
Site should be (as correctly done) updated via SVN. After changes were done, it is necessary for the changes to be published to call svn update on the corresponding folder on the server (see above). That makes the files visible online (actually it copies the the latest svn versions to the server, so copying all the latest changes)...
...then it is necessary to wait awhile (it took about 2 hours) till the changes are visible online
> Update project website
> ----------------------
>
> Key: EMPIREDB-39
> URL: https://issues.apache.org/jira/browse/EMPIREDB-39
> Project: Empire-DB
> Issue Type: Improvement
> Components: Core, Struts2 Extentions
> Affects Versions: empire-db-2.0.5-incubating
> Reporter: Rainer Döbele
> Assignee: Jörg Reiher
> Fix For: empire-db-2.0.5-incubating
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.