You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@openmeetings.apache.org by se...@apache.org on 2011/12/18 13:42:25 UTC
svn commit: r1220385 [3/3] - in /incubator/openmeetings/trunk/singlewebapp:
docs/ docs/images/ xdocs/ xdocs/images/ xdocs/stylesheets/
Modified: incubator/openmeetings/trunk/singlewebapp/docs/svn.html
URL: http://svn.apache.org/viewvc/incubator/openmeetings/trunk/singlewebapp/docs/svn.html?rev=1220385&r1=1220384&r2=1220385&view=diff
==============================================================================
--- incubator/openmeetings/trunk/singlewebapp/docs/svn.html (original)
+++ incubator/openmeetings/trunk/singlewebapp/docs/svn.html Sun Dec 18 12:42:23 2011
@@ -29,7 +29,8 @@ limitations under the License.
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/>
<meta name="author" value="
- Sebastian Wagner">
+ Sebastian Wagner
+ ">
<meta name="email" value="sebawagner@apache.org">
@@ -89,23 +90,23 @@ limitations under the License.
</a>
<hr style="width:100%; color:#999999; background-color:#999999; height:1px; border:0px;"/>
<ul>
- <font color="#000000" face="arial,helvetica,sanserif" size="2pt">
- <li> <a href="./index.html">Home</a>
+ <font color="#000000" face="arial,helvetica,sanserif" size="2pt">
+ <li> <a href="./index.html">Home</a>
</li>
- </font>
- <font color="#000000" face="arial,helvetica,sanserif" size="2pt">
- <li> <a href="./license.html">License</a>
-</li>
- </font>
- <font color="#000000" face="arial,helvetica,sanserif" size="2pt">
- <li> <a href="http://www.apache.org/">ASF</a>
-</li>
- </font>
- <font color="#000000" face="arial,helvetica,sanserif" size="2pt">
- <li> <a href="./downloads.html">Downloads</a>
+ </font>
+ <font color="#000000" face="arial,helvetica,sanserif" size="2pt">
+ <li> <a href="./license.html">License</a>
+</li>
+ </font>
+ <font color="#000000" face="arial,helvetica,sanserif" size="2pt">
+ <li> <a href="http://www.apache.org/">ASF</a>
+</li>
+ </font>
+ <font color="#000000" face="arial,helvetica,sanserif" size="2pt">
+ <li> <a href="./downloads.html">Downloads</a>
</li>
- </font>
- </ul>
+ </font>
+ </ul>
</div>
</div>
</div>
@@ -122,23 +123,23 @@ limitations under the License.
</a>
<hr style="width:100%; color:#999999; background-color:#999999; height:1px; border:0px;"/>
<ul>
- <font color="#000000" face="arial,helvetica,sanserif" size="2pt">
- <li> <a href="./get-involved.html">Get Involved</a>
+ <font color="#000000" face="arial,helvetica,sanserif" size="2pt">
+ <li> <a href="./get-involved.html">Get Involved</a>
</li>
- </font>
- <font color="#000000" face="arial,helvetica,sanserif" size="2pt">
- <li> <a href="./team-list.html">Committers</a>
-</li>
- </font>
- <font color="#000000" face="arial,helvetica,sanserif" size="2pt">
- <li> <a href="./mail-lists.html">Mailing Lists</a>
-</li>
- </font>
- <font color="#000000" face="arial,helvetica,sanserif" size="2pt">
- <li> <a href=".https://cwiki.apache.org/OPENMEETINGS/">Wiki</a>
+ </font>
+ <font color="#000000" face="arial,helvetica,sanserif" size="2pt">
+ <li> <a href="./team-list.html">Committers</a>
+</li>
+ </font>
+ <font color="#000000" face="arial,helvetica,sanserif" size="2pt">
+ <li> <a href="./mail-lists.html">Mailing Lists</a>
+</li>
+ </font>
+ <font color="#000000" face="arial,helvetica,sanserif" size="2pt">
+ <li> <a href=".https://cwiki.apache.org/OPENMEETINGS/">Wiki</a>
</li>
- </font>
- </ul>
+ </font>
+ </ul>
</div>
</div>
</div>
@@ -155,19 +156,50 @@ limitations under the License.
</a>
<hr style="width:100%; color:#999999; background-color:#999999; height:1px; border:0px;"/>
<ul>
- <font color="#000000" face="arial,helvetica,sanserif" size="2pt">
- <li> <a href="./svn.html">Source Code</a>
+ <font color="#000000" face="arial,helvetica,sanserif" size="2pt">
+ <li> <a href="./svn.html">Source Code</a>
</li>
- </font>
- <font color="#000000" face="arial,helvetica,sanserif" size="2pt">
- <li> <a href="http://issues.apache.org/jira/browse/OPENMEETINGS">JIRA</a>
-</li>
- </font>
- <font color="#000000" face="arial,helvetica,sanserif" size="2pt">
- <li> <a href="./dependencies.html">Dependencies</a>
+ </font>
+ <font color="#000000" face="arial,helvetica,sanserif" size="2pt">
+ <li> <a href="http://issues.apache.org/jira/browse/OPENMEETINGS">JIRA</a>
+</li>
+ </font>
+ <font color="#000000" face="arial,helvetica,sanserif" size="2pt">
+ <li> <a href="./dependencies.html">Dependencies</a>
</li>
- </font>
- </ul>
+ </font>
+ </ul>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ <div class="ro">
+ <div class="lo">
+ <div class="ru">
+ <div class="lu">
+ <div class="inhalt">
+
+ <font color="#000000" face="arial,helvetica,sanserif" size="2pt" >
+ <b>Configuration</b>
+ </a>
+ <hr style="width:100%; color:#999999; background-color:#999999; height:1px; border:0px;"/>
+ <ul>
+ <li><font color="#000000" face="arial,helvetica,sanserif" size="2pt">DB Sample Configurations</font>
+ <ul>
+ <li> <a href="./ApacheDerbyConfig.html">Apache Derby</a>
+</li>
+ <li> <a href="./IBMDB2Config.html">IBM DB2</a>
+</li>
+ <li> <a href="./OracleConfig.html">Oracle</a>
+</li>
+ <li> <a href="./MySQLConfig.html">MySQL</a>
+</li>
+ <li> <a href="./PostgresConfig.html">Postgres</a>
+</li>
+ </ul>
+ </li>
+ </ul>
</div>
</div>
</div>
@@ -184,15 +216,19 @@ limitations under the License.
</a>
<hr style="width:100%; color:#999999; background-color:#999999; height:1px; border:0px;"/>
<ul>
- <font color="#000000" face="arial,helvetica,sanserif" size="2pt">
- <li> <a href="./SoapRestAPI.html">SOAP/REST API</a>
+ <font color="#000000" face="arial,helvetica,sanserif" size="2pt">
+ <li> <a href="./SoapRestAPI.html">SOAP/REST API</a>
</li>
- </font>
- <font color="#000000" face="arial,helvetica,sanserif" size="2pt">
- <li> <a href="./RestAPI.html">REST API Sample</a>
+ </font>
+ <font color="#000000" face="arial,helvetica,sanserif" size="2pt">
+ <li> <a href="./RestAPI.html">REST API Sample</a>
+</li>
+ </font>
+ <font color="#000000" face="arial,helvetica,sanserif" size="2pt">
+ <li> <a href="./LdapAndADS.html">Ldap and ADS</a>
</li>
- </font>
- </ul>
+ </font>
+ </ul>
</div>
</div>
</div>
@@ -212,21 +248,29 @@ limitations under the License.
</td></tr>
<tr><td>
<blockquote>
- <p>OpenMeetings uses
-<a class="external" rel="nofollow" href="http://subversion.tigris.org">
-Subversion</a> to manage its source code.
-If you're new to Subversion, you can check out the
-<a href="http://svnbook.red-bean.com/">online book</a> about Subversion.
-Note that we are currently using Subversion 1.1.x (there are separate
-versions of the book covering 1.0 and 1.1).
-</p>
+ <p>
+ OpenMeetings uses
+ <a class="external" rel="nofollow" href="http://subversion.tigris.org">
+ Subversion
+ </a>
+ to manage its source code.
+ If you're new to Subversion, you can check out the
+ <a href="http://svnbook.red-bean.com/">online book</a>
+ about Subversion.
+ Note that we are currently using Subversion 1.1.x (there are separate
+ versions of the book covering 1.0 and 1.1).
+ </p>
<p>
-To receive notice of commits to the repository subscribe to
-<a href="mailto:openmeetings-commits@incubator.apache.org">
-openmeetings-commits@incubator.apache.org</a> by sending email to
-<a href="mailto:openmeetings-commits-subscribe@incubator.apache.org">
-openmeetings-commits-subscribe@incubator.apache.org</a>.
-</p>
+ To receive notice of commits to the repository subscribe to
+ <a href="mailto:openmeetings-commits@incubator.apache.org">
+ openmeetings-commits@incubator.apache.org
+ </a>
+ by sending email to
+ <a href="mailto:openmeetings-commits-subscribe@incubator.apache.org">
+ openmeetings-commits-subscribe@incubator.apache.org
+ </a>
+ .
+ </p>
</blockquote>
</p>
</td></tr>
@@ -242,10 +286,12 @@ openmeetings-commits-subscribe@incubator
<tr><td>
<blockquote>
<p>
-If you just want to browse the source code, you can use the
-<a class="external" rel="nofollow" href="http://svn.apache.org/viewcvs/incubator/openmeetings">
-ViewCVS web interface</a> to Subversion. This is current at all times.
-</p>
+ If you just want to browse the source code, you can use the
+ <a class="external" rel="nofollow" href="http://svn.apache.org/viewcvs/incubator/openmeetings">
+ ViewCVS web interface
+ </a>
+ to Subversion. This is current at all times.
+ </p>
</blockquote>
</p>
</td></tr>
@@ -260,13 +306,15 @@ ViewCVS web interface</a> to Subversion.
</td></tr>
<tr><td>
<blockquote>
- <p>Anyone can check code out of Subversion. You only need to specify a
-username and password to update the Subversion repository, and only
-OpenMeetings committers can do that.
-If you are a committer, are working from behind a firewall, or are
-connected to the internet through a proxy server, please see the sections
-below for more information.
-</p>
+ <p>Anyone can check code out of Subversion. You only need to specify
+ a
+ username and password to update the Subversion repository, and only
+ OpenMeetings committers can do that.
+ If you are a committer, are working from behind a firewall, or are
+ connected to the internet through a proxy server, please see the
+ sections
+ below for more information.
+ </p>
<table border="0" cellspacing="0" cellpadding="0" width="100%">
<tr><td bgcolor="#EFEFEF">
<font color="#000000" face="arial,helvetica,sanserif">
@@ -276,12 +324,15 @@ below for more information.
<tr><td>
<blockquote>
<p>Use a command like:</p>
- <pre>% svn checkout http://svn.apache.org/repos/asf/incubator/openmeetings </pre>
- <p>Once you have OpenMeetings checked out you can update the source
-by executing the following command from within the openmeetings directory. </p>
+ <pre>% svn checkout
+ http://svn.apache.org/repos/asf/incubator/openmeetings </pre>
+ <p>Once you have OpenMeetings checked out you can update the source
+ by executing the following command from within the openmeetings
+ directory.
+ </p>
<pre>
-% svn update
-</pre>
+ % svn update
+ </pre>
</blockquote>
</td></tr>
<tr><td><br/></td></tr>
@@ -294,12 +345,15 @@ by executing the following command from
</td></tr>
<tr><td>
<blockquote>
- <p>For those users who are stuck behind a corporate firewall which is
-blocking http access to the Subversion repository, you can try to access it
-via HTTPS: </p>
+ <p>For those users who are stuck behind a corporate firewall which
+ is
+ blocking http access to the Subversion repository, you can try to access it
+ via HTTPS:
+ </p>
<pre>
-% svn checkout https://svn.apache.org/repos/asf/incubator/openmeetings
-</pre>
+ % svn checkout
+ https://svn.apache.org/repos/asf/incubator/openmeetings
+ </pre>
</blockquote>
</td></tr>
<tr><td><br/></td></tr>
@@ -312,23 +366,27 @@ via HTTPS: </p>
</td></tr>
<tr><td>
<blockquote>
- <p>The Subversion client can go through a proxy, if you configure it
-to do so. First, edit your "servers" configuration file to indicate which
-proxy to use. The files location depends on your operating system.
-On Linux or Unix it is located in the directory "~/.subversion".
-On Windows it is in "%APPDATA%\Subversion". (Try "echo %APPDATA%",
-note this is a hidden directory.) </p>
- <p>There are comments in the file explaining what to do. If you don't have
-that file, get the latest Subversion client and run any command; this will
-cause the configuration directory and template files to be created.
-</p>
- <p>Example : Edit the 'servers' file and add something like :
-</p>
+ <p>The Subversion client can go through a proxy, if you configure it
+ to do so. First, edit your "servers" configuration file to indicate
+ which
+ proxy to use. The files location depends on your operating system.
+ On Linux or Unix it is located in the directory "~/.subversion".
+ On Windows it is in "%APPDATA%\Subversion". (Try "echo %APPDATA%",
+ note this is a hidden directory.)
+ </p>
+ <p>There are comments in the file explaining what to do. If you
+ don't have
+ that file, get the latest Subversion client and run any command; this
+ will
+ cause the configuration directory and template files to be created.
+ </p>
+ <p>Example : Edit the 'servers' file and add something like :
+ </p>
<pre>
-[global]
-http-proxy-host = your.proxy.name
-http-proxy-port = 3128
-</pre>
+ [global]
+ http-proxy-host = your.proxy.name
+ http-proxy-port = 3128
+ </pre>
</blockquote>
</td></tr>
<tr><td><br/></td></tr>
@@ -341,13 +399,15 @@ http-proxy-port = 3128
</td></tr>
<tr><td>
<blockquote>
- <p>Everyone can access the Apache Podling Subversion repository via HTTPS,
-but OpenMeetings Committers must checkout the Subversion repository
-via HTTPS.
-</p>
+ <p>Everyone can access the Apache Podling Subversion repository via
+ HTTPS,
+ but OpenMeetings Committers must checkout the Subversion repository
+ via HTTPS.
+ </p>
<pre>
-% svn checkout https://svn.apache.org/repos/asf/incubator/openmeetings
-</pre>
+ % svn checkout
+ https://svn.apache.org/repos/asf/incubator/openmeetings
+ </pre>
</blockquote>
</td></tr>
<tr><td><br/></td></tr>
@@ -374,21 +434,25 @@ via HTTPS.
</td></tr>
<tr><td>
<blockquote>
- <p>If you make changes to OpenMeetings, and would like to contribute
-it to the project, you should open a JIRA issue and discuss the merits
-of the proposal with the developer community. If there is agreement,
-create a patch and attach it to the JIRA issue.
-</p>
+ <p>If you make changes to OpenMeetings, and would like to contribute
+ it to the project, you should open a JIRA issue and discuss the
+ merits
+ of the proposal with the developer community. If there is agreement,
+ create a patch and attach it to the JIRA issue.
+ </p>
<p>
-To create a patch, execute the svn diff command. This creates a patch that
-can easily be uploaded to a JIRA issue. A good name for the patch includes
-the JIRA issue name, e.g. OPENMEETINGS-104.patch. If there are several patches
-for the same JIRA issue, you might include your initials, e.g.
-OPENMEETINGS-104.clr.patch
-</p>
+ To create a patch, execute the svn diff command. This creates a patch
+ that
+ can easily be uploaded to a JIRA issue. A good name for the patch
+ includes
+ the JIRA issue name, e.g. OPENMEETINGS-104.patch. If there are several
+ patches
+ for the same JIRA issue, you might include your initials, e.g.
+ OPENMEETINGS-104.clr.patch
+ </p>
<pre>
-% svn diff > OPENMEETINGS-104.clr.patch
-</pre>
+ % svn diff > OPENMEETINGS-104.clr.patch
+ </pre>
</blockquote>
</td></tr>
<tr><td><br/></td></tr>
@@ -402,30 +466,32 @@ OPENMEETINGS-104.clr.patch
<tr><td>
<blockquote>
<p>
-To commit changes to the subversion repository, you must be an
-OpenMeetings committer. See <a href="get-involved.html">get involved</a>
-for information on how to become a committer and how to set up your
-password once you become a committer.
-</p>
+ To commit changes to the subversion repository, you must be an
+ OpenMeetings committer. See
+ <a href="get-involved.html">get involved</a>
+ for information on how to become a committer and how to set up your
+ password once you become a committer.
+ </p>
<p>
-Once your password is set, you can use a command like this to commit:
-</p>
+ Once your password is set, you can use a command like this to commit:
+ </p>
<pre>
-$> svn commit --username your-username
-Authentication realm: <https://svn.apache.org:443> ASF Committers
-Password for 'your-username': your-password
-</pre>
- <p>You can also pass your password on the command line directly, but
-this is a security problem on multiuser unix computers (the command line
-arguments are available via the ps command). Here is the command if you
-are Windows or a single user unix computer:
-</p>
+ $> svn commit --username your-username
+ Authentication realm: <https://svn.apache.org:443> ASF Committers
+ Password for 'your-username': your-password
+ </pre>
+ <p>You can also pass your password on the command line directly, but
+ this is a security problem on multiuser unix computers (the command
+ line
+ arguments are available via the ps command). Here is the command if you
+ are Windows or a single user unix computer:
+ </p>
<pre>
-$> svn commit --username your-username --password your-password
-</pre>
- <p>Remember to replace 'your-username' and 'your-password' with
-your actual username and password on svn.apache.org.
-</p>
+ $> svn commit --username your-username --password your-password
+ </pre>
+ <p>Remember to replace 'your-username' and 'your-password' with
+ your actual username and password on svn.apache.org.
+ </p>
</blockquote>
</td></tr>
<tr><td><br/></td></tr>
@@ -445,14 +511,14 @@ your actual username and password on svn
<tr><td>
<blockquote>
<p>
-<!-- ***************** TBD ************************** -->
-<!-- ***************** TBD ************************** -->
-<!-- ***************** TBD ************************** -->
-<!-- ***************** TBD ************************** -->
-<!-- ***************** TBD ************************** -->
-<!-- ***************** TBD ************************** -->
-<!-- ***************** TBD ************************** -->
-</p>
+ <!-- ***************** TBD ************************** -->
+ <!-- ***************** TBD ************************** -->
+ <!-- ***************** TBD ************************** -->
+ <!-- ***************** TBD ************************** -->
+ <!-- ***************** TBD ************************** -->
+ <!-- ***************** TBD ************************** -->
+ <!-- ***************** TBD ************************** -->
+ </p>
</blockquote>
</p>
</td></tr>
@@ -467,20 +533,24 @@ your actual username and password on svn
</td></tr>
<tr><td>
<blockquote>
- <p>If you use Subversion on Windows under cygwin, you may find that the
-Subversion client automatically assigns the executable property to
-non-executable files. In that case, you would see this at the bottom of
-an <em>svn diff</em> of the file:
-</p>
+ <p>
+ If you use Subversion on Windows under cygwin, you may find that the
+ Subversion client automatically assigns the executable property to
+ non-executable files. In that case, you would see this at the bottom
+ of
+ an
+ <em>svn diff</em>
+ of the file:
+ </p>
<pre>
-Property changes on: test/sql/derby/datastoreidentity/schema1.sql
-___________________________________________________________________
-Name: svn:executable
- + *
-</pre>
- <p>This section explains the source of the problem and suggests some
-actions to avoid it.
-</p>
+ Property changes on: test/sql/derby/datastoreidentity/schema1.sql
+ ___________________________________________________________________
+ Name: svn:executable
+ + *
+ </pre>
+ <p>This section explains the source of the problem and suggests some
+ actions to avoid it.
+ </p>
<table border="0" cellspacing="0" cellpadding="0" width="100%">
<tr><td bgcolor="#EFEFEF">
<font color="#000000" face="arial,helvetica,sanserif">
@@ -489,24 +559,31 @@ actions to avoid it.
</td></tr>
<tr><td>
<blockquote>
- <p>Subversion carries executable information in the built-in property
-called svn:executable. This property, unlike others, may be present
-or absent, but it has no value. You can add it or delete it, but you
-cannot change its value.
-</p>
- <p>In theory, Subversion ignores Windows file permissions and by default
-does not set svn:executable. However, cygwin svn acts like Unix svn and
-determines the svn:executable property based on file permissions.
-</p>
- <p>If you create a file from the cygwin command line, by default it is
-executable only if the filename ends with .bat, .com or .exe, or if its
-content starts with #!. [This is what the doc says, but you may see -x
-for all files.] If you create a file using a Windows tool, by default
-its Windows permissions are executable by all. Cygwin interprets the
-Unix-style permissions this way as well. If the file is executable by all,
-cygwin svn sets the svn:executable property on the file when you invoke
-<em>svn add</em>.
-</p>
+ <p>Subversion carries executable information in the built-in
+ property
+ called svn:executable. This property, unlike others, may be present
+ or absent, but it has no value. You can add it or delete it, but you
+ cannot change its value.
+ </p>
+ <p>In theory, Subversion ignores Windows file permissions and by
+ default
+ does not set svn:executable. However, cygwin svn acts like Unix svn and
+ determines the svn:executable property based on file permissions.
+ </p>
+ <p>
+ If you create a file from the cygwin command line, by default it is
+ executable only if the filename ends with .bat, .com or .exe, or if
+ its
+ content starts with #!. [This is what the doc says, but you may see -x
+ for all files.] If you create a file using a Windows tool, by default
+ its Windows permissions are executable by all. Cygwin interprets
+ the
+ Unix-style permissions this way as well. If the file is executable by all,
+ cygwin svn sets the svn:executable property on the file when you
+ invoke
+ <em>svn add</em>
+ .
+ </p>
</blockquote>
</td></tr>
<tr><td><br/></td></tr>
@@ -519,16 +596,18 @@ cygwin svn sets the svn:executable prope
</td></tr>
<tr><td>
<blockquote>
- <p>You can use svn propdel to remove the svn:executable property from your
-working copy.
-</p>
+ <p>You can use svn propdel to remove the svn:executable property
+ from your
+ working copy.
+ </p>
<pre>
- svn propdel -R svn:executable .
-</pre>
- <p>will recursively remove the svn:executable property from all of the
-files below the current directory. You can use this and commit the
-files to clean the repository if necessary.
-</p>
+ svn propdel -R svn:executable .
+ </pre>
+ <p>will recursively remove the svn:executable property from all of
+ the
+ files below the current directory. You can use this and commit the
+ files to clean the repository if necessary.
+ </p>
</blockquote>
</td></tr>
<tr><td><br/></td></tr>
@@ -541,45 +620,63 @@ files to clean the repository if necessa
</td></tr>
<tr><td>
<blockquote>
- <p>Windows/cygwin users who don't want to have to think about using <em>svn
-propdel</em> or <em>chmod</em> on each added file can use a non-cygwin
-version of svn. The Subversion 1.2.3 Win32 binaries, downloadable from the
-link at the bottom of <a rel="nofollow" href="http://subversion.tigris.org/project_packages.html">
-http://subversion.tigris.org/project_packages.html</a>, appear to work
-well. After installation add the svn.exe location to your Windows PATH
-variable. If you are switching from cygwin svn to Win32 svn </p>
+ <p>
+ Windows/cygwin users who don't want to have to think about using
+ <em>svn
+ propdel
+ </em>
+ or
+ <em>chmod</em>
+ on each added file can use a non-cygwin
+ version of svn. The Subversion 1.2.3 Win32 binaries, downloadable from the
+ link at the bottom of
+ <a rel="nofollow" href="http://subversion.tigris.org/project_packages.html">
+ http://subversion.tigris.org/project_packages.html
+ </a>
+ , appear to work
+ well. After installation add the svn.exe location to your Windows PATH
+ variable. If you are switching from cygwin svn to Win32 svn
+ </p>
<ol type="1">
-<li>
-<p>Remove the subversion component from your cygwin installation
-because when svn is invoked from a cygwin window, the cygwin version is
-found even if your cygwin/bin directory is later on the path. (In the
-Select Packages window of the setup wizard, navigate to the subversion
-package in the Devel. category. Click on the status icon until Uninstall
-is displayed. Click next and continue through the wizard until installation
-is complete.)
-</p>
-</li>
-<li>
-<p>Copy the servers file and the auth folder from the sygwin ~/.subversion
-directory to C:\Documents and
-Settings\<user>\Application Data\Subversion used by Win32
-subversion.
-</p>
-</li>
-</ol>
- <p>Note that windows svn uses backslash as the path separator when
-displaying file names. You cannot just copy and paste this file name
-to another svn command when running from within a cygwin shell.
-You need to enclose the file name into double quotes.
-</p>
- <p>Alternatively, Windows users can set file permissions in Windows
-Explorer. (Right-click on the top-level folder & select Properties.
-Select the Security tab. Click Advanced. Remove all instances of
-Read & Execute from the Permission Entries. Click "Reset permissions
-on all child objects and enable propogations of inheritable permissions".
-Click Apply. OK. OK.) You will have to do this again when you do a clean
-checkout to a new directory.
-</p>
+ <li>
+ <p>Remove the subversion component from your cygwin installation
+ because when svn is invoked from a cygwin window, the cygwin
+ version is
+ found even if your cygwin/bin directory is later on the path. (In the
+ Select Packages window of the setup wizard, navigate to the
+ subversion
+ package in the Devel. category. Click on the status icon until Uninstall
+ is displayed. Click next and continue through the wizard until
+ installation
+ is complete.)
+ </p>
+ </li>
+ <li>
+ <p>Copy the servers file and the auth folder from the sygwin
+ ~/.subversion
+ directory to C:\Documents and
+ Settings\<user>\Application Data\Subversion used by Win32
+ subversion.
+ </p>
+ </li>
+ </ol>
+ <p>Note that windows svn uses backslash as the path separator when
+ displaying file names. You cannot just copy and paste this file
+ name
+ to another svn command when running from within a cygwin shell.
+ You need to enclose the file name into double quotes.
+ </p>
+ <p>Alternatively, Windows users can set file permissions in Windows
+ Explorer. (Right-click on the top-level folder & select
+ Properties.
+ Select the Security tab. Click Advanced. Remove all instances of
+ Read & Execute from the Permission Entries. Click "Reset
+ permissions
+ on all child objects and enable propogations of inheritable
+ permissions".
+ Click Apply. OK. OK.) You will have to do this again when you do a clean
+ checkout to a new directory.
+ </p>
</blockquote>
</td></tr>
<tr><td><br/></td></tr>
Modified: incubator/openmeetings/trunk/singlewebapp/docs/team-list.html
URL: http://svn.apache.org/viewvc/incubator/openmeetings/trunk/singlewebapp/docs/team-list.html?rev=1220385&r1=1220384&r2=1220385&view=diff
==============================================================================
--- incubator/openmeetings/trunk/singlewebapp/docs/team-list.html (original)
+++ incubator/openmeetings/trunk/singlewebapp/docs/team-list.html Sun Dec 18 12:42:23 2011
@@ -89,23 +89,23 @@ limitations under the License.
</a>
<hr style="width:100%; color:#999999; background-color:#999999; height:1px; border:0px;"/>
<ul>
- <font color="#000000" face="arial,helvetica,sanserif" size="2pt">
- <li> <a href="./index.html">Home</a>
+ <font color="#000000" face="arial,helvetica,sanserif" size="2pt">
+ <li> <a href="./index.html">Home</a>
</li>
- </font>
- <font color="#000000" face="arial,helvetica,sanserif" size="2pt">
- <li> <a href="./license.html">License</a>
-</li>
- </font>
- <font color="#000000" face="arial,helvetica,sanserif" size="2pt">
- <li> <a href="http://www.apache.org/">ASF</a>
-</li>
- </font>
- <font color="#000000" face="arial,helvetica,sanserif" size="2pt">
- <li> <a href="./downloads.html">Downloads</a>
+ </font>
+ <font color="#000000" face="arial,helvetica,sanserif" size="2pt">
+ <li> <a href="./license.html">License</a>
+</li>
+ </font>
+ <font color="#000000" face="arial,helvetica,sanserif" size="2pt">
+ <li> <a href="http://www.apache.org/">ASF</a>
+</li>
+ </font>
+ <font color="#000000" face="arial,helvetica,sanserif" size="2pt">
+ <li> <a href="./downloads.html">Downloads</a>
</li>
- </font>
- </ul>
+ </font>
+ </ul>
</div>
</div>
</div>
@@ -122,23 +122,23 @@ limitations under the License.
</a>
<hr style="width:100%; color:#999999; background-color:#999999; height:1px; border:0px;"/>
<ul>
- <font color="#000000" face="arial,helvetica,sanserif" size="2pt">
- <li> <a href="./get-involved.html">Get Involved</a>
+ <font color="#000000" face="arial,helvetica,sanserif" size="2pt">
+ <li> <a href="./get-involved.html">Get Involved</a>
</li>
- </font>
- <font color="#000000" face="arial,helvetica,sanserif" size="2pt">
- <li> <a href="./team-list.html">Committers</a>
-</li>
- </font>
- <font color="#000000" face="arial,helvetica,sanserif" size="2pt">
- <li> <a href="./mail-lists.html">Mailing Lists</a>
-</li>
- </font>
- <font color="#000000" face="arial,helvetica,sanserif" size="2pt">
- <li> <a href=".https://cwiki.apache.org/OPENMEETINGS/">Wiki</a>
+ </font>
+ <font color="#000000" face="arial,helvetica,sanserif" size="2pt">
+ <li> <a href="./team-list.html">Committers</a>
+</li>
+ </font>
+ <font color="#000000" face="arial,helvetica,sanserif" size="2pt">
+ <li> <a href="./mail-lists.html">Mailing Lists</a>
+</li>
+ </font>
+ <font color="#000000" face="arial,helvetica,sanserif" size="2pt">
+ <li> <a href=".https://cwiki.apache.org/OPENMEETINGS/">Wiki</a>
</li>
- </font>
- </ul>
+ </font>
+ </ul>
</div>
</div>
</div>
@@ -155,19 +155,50 @@ limitations under the License.
</a>
<hr style="width:100%; color:#999999; background-color:#999999; height:1px; border:0px;"/>
<ul>
- <font color="#000000" face="arial,helvetica,sanserif" size="2pt">
- <li> <a href="./svn.html">Source Code</a>
+ <font color="#000000" face="arial,helvetica,sanserif" size="2pt">
+ <li> <a href="./svn.html">Source Code</a>
</li>
- </font>
- <font color="#000000" face="arial,helvetica,sanserif" size="2pt">
- <li> <a href="http://issues.apache.org/jira/browse/OPENMEETINGS">JIRA</a>
-</li>
- </font>
- <font color="#000000" face="arial,helvetica,sanserif" size="2pt">
- <li> <a href="./dependencies.html">Dependencies</a>
+ </font>
+ <font color="#000000" face="arial,helvetica,sanserif" size="2pt">
+ <li> <a href="http://issues.apache.org/jira/browse/OPENMEETINGS">JIRA</a>
+</li>
+ </font>
+ <font color="#000000" face="arial,helvetica,sanserif" size="2pt">
+ <li> <a href="./dependencies.html">Dependencies</a>
</li>
- </font>
- </ul>
+ </font>
+ </ul>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ <div class="ro">
+ <div class="lo">
+ <div class="ru">
+ <div class="lu">
+ <div class="inhalt">
+
+ <font color="#000000" face="arial,helvetica,sanserif" size="2pt" >
+ <b>Configuration</b>
+ </a>
+ <hr style="width:100%; color:#999999; background-color:#999999; height:1px; border:0px;"/>
+ <ul>
+ <li><font color="#000000" face="arial,helvetica,sanserif" size="2pt">DB Sample Configurations</font>
+ <ul>
+ <li> <a href="./ApacheDerbyConfig.html">Apache Derby</a>
+</li>
+ <li> <a href="./IBMDB2Config.html">IBM DB2</a>
+</li>
+ <li> <a href="./OracleConfig.html">Oracle</a>
+</li>
+ <li> <a href="./MySQLConfig.html">MySQL</a>
+</li>
+ <li> <a href="./PostgresConfig.html">Postgres</a>
+</li>
+ </ul>
+ </li>
+ </ul>
</div>
</div>
</div>
@@ -184,15 +215,19 @@ limitations under the License.
</a>
<hr style="width:100%; color:#999999; background-color:#999999; height:1px; border:0px;"/>
<ul>
- <font color="#000000" face="arial,helvetica,sanserif" size="2pt">
- <li> <a href="./SoapRestAPI.html">SOAP/REST API</a>
+ <font color="#000000" face="arial,helvetica,sanserif" size="2pt">
+ <li> <a href="./SoapRestAPI.html">SOAP/REST API</a>
</li>
- </font>
- <font color="#000000" face="arial,helvetica,sanserif" size="2pt">
- <li> <a href="./RestAPI.html">REST API Sample</a>
+ </font>
+ <font color="#000000" face="arial,helvetica,sanserif" size="2pt">
+ <li> <a href="./RestAPI.html">REST API Sample</a>
+</li>
+ </font>
+ <font color="#000000" face="arial,helvetica,sanserif" size="2pt">
+ <li> <a href="./LdapAndADS.html">Ldap and ADS</a>
</li>
- </font>
- </ul>
+ </font>
+ </ul>
</div>
</div>
</div>
Added: incubator/openmeetings/trunk/singlewebapp/xdocs/ApacheDerbyConfig.xml
URL: http://svn.apache.org/viewvc/incubator/openmeetings/trunk/singlewebapp/xdocs/ApacheDerbyConfig.xml?rev=1220385&view=auto
==============================================================================
--- incubator/openmeetings/trunk/singlewebapp/xdocs/ApacheDerbyConfig.xml (added)
+++ incubator/openmeetings/trunk/singlewebapp/xdocs/ApacheDerbyConfig.xml Sun Dec 18 12:42:23 2011
@@ -0,0 +1,55 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+
+<!-- Copyright 2006 The Apache Software Foundation Licensed under the Apache
+ License, Version 2.0 (the "License"); you may not use this file except in
+ compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0
+ Unless required by applicable law or agreed to in writing, software distributed
+ under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES
+ OR CONDITIONS OF ANY KIND, either express or implied. See the License for
+ the specific language governing permissions and limitations under the License. -->
+
+
+<document>
+
+ <properties>
+ <title>Apache Derby Configuration</title>
+ <author email="sebawagner@incubator.apache.org">
+ Apache OpenMeetings Documentation Team
+ </author>
+ </properties>
+
+ <body>
+ <section name="Apache Derby Configuration">
+
+ <p>
+ OpenMeetings default configuration is to use Apache Derby.
+ </p>
+
+ <p>
+ It is recommended for production environments and high
+ availibility to change to an usual relational database like MySQL,
+ Postgres or DB2.
+ </p>
+ <p>
+ For more information about Apache Derby see
+ <a href="http://db.apache.org/derby/">http://db.apache.org/derby/</a>
+ </p>
+
+ <p>
+ There is a sample configuration for Apache Derby that ships with
+ every release in:
+ <br />
+ /webapps/openmeetings/WEB-INF/classes/META-INF/derby_persistence.xml
+ </p>
+
+ <p>
+ If you encounter issues, you can drop the db again and delete the
+ file /webapps/openmeetings/conf/install.xml and then run the web
+ based installer again
+ </p>
+
+ </section>
+
+ </body>
+
+</document>
Added: incubator/openmeetings/trunk/singlewebapp/xdocs/IBMDB2Config.xml
URL: http://svn.apache.org/viewvc/incubator/openmeetings/trunk/singlewebapp/xdocs/IBMDB2Config.xml?rev=1220385&view=auto
==============================================================================
--- incubator/openmeetings/trunk/singlewebapp/xdocs/IBMDB2Config.xml (added)
+++ incubator/openmeetings/trunk/singlewebapp/xdocs/IBMDB2Config.xml Sun Dec 18 12:42:23 2011
@@ -0,0 +1,92 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+
+<!-- Copyright 2006 The Apache Software Foundation Licensed under the Apache
+ License, Version 2.0 (the "License"); you may not use this file except in
+ compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0
+ Unless required by applicable law or agreed to in writing, software distributed
+ under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES
+ OR CONDITIONS OF ANY KIND, either express or implied. See the License for
+ the specific language governing permissions and limitations under the License. -->
+
+
+<document>
+
+ <properties>
+ <title>IBM DB2 Configuration</title>
+ <author email="sebawagner@incubator.apache.org">
+ Apache OpenMeetings Documentation Team
+ </author>
+ </properties>
+
+ <body>
+ <section name="IBM DB2 Configuration">
+
+ <subsection name="Before you start">
+ <i>Tested with IBM DB2 Express-C 9.7.x</i>
+ <ul>
+ <li>
+ Get the IBM Data Server Driver for JDBC and SQLJ from IBM website:
+ <a
+ href="https://www14.software.ibm.com/webapp/iwm/web/preLogin.do?source=swg-idsdjs">https://www14.software.ibm.com/webapp/iwm/web/preLogin.do?source=swg-idsdjs
+ </a>
+ </li>
+ <li>Copy JDBC driver db2jcc4.jar to
+ webapps/openmeetings/WEB-INF/lib/
+ </li>
+ <li>
+ Create database for OpenMeetings using a pagesize bigger or equal
+ 8K, sample query:
+ <br />
+ <div class="xmlcode">
+ CREATE DATABASE openmeet AUTOMATIC STORAGE YES ON 'C:' DBPATH ON 'C:'
+ USING CODESET UTF-8 TERRITORY DE COLLATE USING System PAGESIZE 16
+ K
+ </div>
+ </li>
+ <li>If you encounter issues, you can drop the db again and delete
+ the file $red5/webapps/openmeetings/conf/install.xml and then run
+ the web based installer again </li>
+ </ul>
+ </subsection>
+
+ <subsection name="Steps todo">
+ <ul>
+ <li>
+ Rename:
+ <br />
+ $red5/webapps/openmeetings/WEB-INF/classes/META-INF/db2_persistence.xml
+ <br />
+ to
+ <br />
+ $red5/webapps/openmeetings/WEB-INF/classes/META-INF/persistence.xml
+ </li>
+ <li>
+ Prepare Database Settings - go to
+ openmeetings_version_no_xx/webapps/openmeetings/WEB-INF/classes/META-INF/persistence.xml
+ <br />
+ Alter config values in persistence.xml connectionURL, username and
+ password with your values
+ </li>
+ <li>
+ Run red5-service and goto the web-based installer:
+ http://localhost:5080/openmeetings/install
+ </li>
+ </ul>
+ </subsection>
+
+ <subsection name="DB2 Sample Configuration">
+ <p>
+ There is a sample configuration for IBM DB2 that ships with
+ every
+ release in:
+ <br />
+ /webapps/openmeetings/WEB-INF/classes/META-INF/db2_persistence.xml
+ </p>
+ </subsection>
+
+
+ </section>
+
+ </body>
+
+</document>
Added: incubator/openmeetings/trunk/singlewebapp/xdocs/LdapAndADS.xml
URL: http://svn.apache.org/viewvc/incubator/openmeetings/trunk/singlewebapp/xdocs/LdapAndADS.xml?rev=1220385&view=auto
==============================================================================
--- incubator/openmeetings/trunk/singlewebapp/xdocs/LdapAndADS.xml (added)
+++ incubator/openmeetings/trunk/singlewebapp/xdocs/LdapAndADS.xml Sun Dec 18 12:42:23 2011
@@ -0,0 +1,54 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!-- Copyright 2006 The Apache Software Foundation Licensed under the Apache
+ License, Version 2.0 (the "License"); you may not use this file except in
+ compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0
+ Unless required by applicable law or agreed to in writing, software distributed
+ under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES
+ OR CONDITIONS OF ANY KIND, either express or implied. See the License for
+ the specific language governing permissions and limitations under the License. -->
+<document>
+
+ <properties>
+ <title>Home</title>
+ <author email="sebawagner@apache.org">
+ Sebastian Wagner
+ </author>
+ </properties>
+
+ <body>
+
+ <section name="LDAP and Active Directory Integration">
+
+ <p> In: $RED5_HOME/webapps/openmeetings/conf<br/>
+
+ you will find sample configurations for LDAP and Active Directory. The
+ nature of those Directory Servers are that they are individual for
+ every organization, so you have to modify of course at least the
+ path to your user-base et cetera.<br/>
+ <br/>
+ To activate any of those configurations you have to login into
+ OpenMeetings, goto Administration > Ldap.
+ </p>
+
+ <img src="/images/ldap_screen.png" title="OpenMeetingsLdapScreenShot" />
+
+ <p>
+ Import is that you configure LDAP_SEARCH_PATH so that it points to the node of your directory server that contains the users
+ </p>
+
+ <p>
+ If you have multiple search paths you can either try to define a search path that points to multiple nodes or define multiple ldap configurations.
+ </p>
+
+ <p>
+ Successful integration is also reported with Novell eDirectory
+ </p>
+
+ <p>
+ You can configure multiple domains or different user-paths in the Administration of OpenMeetings.
+ </p>
+
+ </section>
+
+ </body>
+</document>
\ No newline at end of file
Added: incubator/openmeetings/trunk/singlewebapp/xdocs/MySQLConfig.xml
URL: http://svn.apache.org/viewvc/incubator/openmeetings/trunk/singlewebapp/xdocs/MySQLConfig.xml?rev=1220385&view=auto
==============================================================================
--- incubator/openmeetings/trunk/singlewebapp/xdocs/MySQLConfig.xml (added)
+++ incubator/openmeetings/trunk/singlewebapp/xdocs/MySQLConfig.xml Sun Dec 18 12:42:23 2011
@@ -0,0 +1,84 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+
+<!-- Copyright 2006 The Apache Software Foundation Licensed under the Apache
+ License, Version 2.0 (the "License"); you may not use this file except in
+ compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0
+ Unless required by applicable law or agreed to in writing, software distributed
+ under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES
+ OR CONDITIONS OF ANY KIND, either express or implied. See the License for
+ the specific language governing permissions and limitations under the License. -->
+
+
+<document>
+
+ <properties>
+ <title>MySQL Configuration</title>
+ <author email="sebawagner@incubator.apache.org">
+ Apache OpenMeetings Documentation Team
+ </author>
+ </properties>
+
+ <body>
+ <section name="MySQL Configuration">
+
+ <subsection name="Before you start">
+ <ul>
+ <li>Make sure that you have set utf8 as
+ default/server-character-set in your MySQL configuration (my.cnf)
+ before you start the installation process of OpenMeetings!
+ </li>
+ <li>
+ make sure MySQL is listening on TCP/IP connections!
+ <br />
+ To verify if MySQL connection is working: OpenMeetings will
+ automatically create all tables in the database and all tables
+ should have utf8 as encoding/collation!
+ </li>
+ <li>If you encounter issues, you can drop the db again and delete
+ the file $red5/webapps/openmeetings/conf/install.xml and then run
+ the web based installer again
+ </li>
+ </ul>
+ </subsection>
+
+ <subsection name="Steps todo">
+ <ul>
+ <li>
+ Rename:
+ <br />
+ $red5/webapps/openmeetings/WEB-INF/classes/META-INF/mysql_persistence.xml
+ <br />
+ to
+ <br />
+ $red5/webapps/openmeetings/WEB-INF/classes/META-INF/persistence.xml
+ </li>
+ <li>
+ Prepare Database Settings - go to
+ openmeetings_version_no_xx/webapps/openmeetings/WEB-INF/classes/META-INF/persistence.xml
+ <br />
+ Alter config values in persistence.xml DB_HOST USER_NAME USER_PASS
+ with your values
+ </li>
+ <li>
+ Run red5-service and goto the web-based installer:
+ http://localhost:5080/openmeetings/install
+ </li>
+ </ul>
+ </subsection>
+
+ <subsection name="MySQL Sample Configuration">
+ <p>
+ There is a sample configuration for MySQL that ships with
+ every
+ release in:
+ <br />
+ /webapps/openmeetings/WEB-INF/classes/META-INF/mysql_persistence.xml
+ </p>
+ </subsection>
+
+
+ </section>
+
+ </body>
+
+</document>
Added: incubator/openmeetings/trunk/singlewebapp/xdocs/OracleConfig.xml
URL: http://svn.apache.org/viewvc/incubator/openmeetings/trunk/singlewebapp/xdocs/OracleConfig.xml?rev=1220385&view=auto
==============================================================================
--- incubator/openmeetings/trunk/singlewebapp/xdocs/OracleConfig.xml (added)
+++ incubator/openmeetings/trunk/singlewebapp/xdocs/OracleConfig.xml Sun Dec 18 12:42:23 2011
@@ -0,0 +1,76 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+
+<!-- Copyright 2006 The Apache Software Foundation Licensed under the Apache
+ License, Version 2.0 (the "License"); you may not use this file except in
+ compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0
+ Unless required by applicable law or agreed to in writing, software distributed
+ under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES
+ OR CONDITIONS OF ANY KIND, either express or implied. See the License for
+ the specific language governing permissions and limitations under the License. -->
+
+
+<document>
+
+ <properties>
+ <title>IBM DB2 Configuration</title>
+ <author email="sebawagner@incubator.apache.org">
+ Apache OpenMeetings Documentation Team
+ </author>
+ </properties>
+
+ <body>
+ <section name="IBM DB2 Configuration">
+
+ <subsection name="Before you start">
+ <ul>
+ <li>Download the latest JDBC Driver from Oracle for your database
+ version. Place those JARs into
+ $Red5/webapps/openmeetings/WEB-INF/lib
+ </li>
+ <li>If you encounter issues, you can drop the db again and delete
+ the file $red5/webapps/openmeetings/conf/install.xml and then run
+ the web based installer again
+ </li>
+ </ul>
+ </subsection>
+
+ <subsection name="Steps todo">
+ <ul>
+ <li>
+ Rename:
+ <br />
+ $red5/webapps/openmeetings/WEB-INF/classes/META-INF/oracle_persistence.xml
+ <br />
+ to
+ <br />
+ $red5/webapps/openmeetings/WEB-INF/classes/META-INF/persistence.xml
+ </li>
+ <li>
+ Prepare Database Settings - go to
+ openmeetings_version_no_xx/webapps/openmeetings/WEB-INF/classes/META-INF/persistence.xml
+ <br />
+ Alter config values in persistence.xml connectionURL, username and
+ password with your values
+ </li>
+ <li>
+ Run red5-service and goto the web-based installer:
+ http://localhost:5080/openmeetings/install
+ </li>
+ </ul>
+ </subsection>
+
+ <subsection name="Oracle Sample Configuration">
+ <p>
+ There is a sample configuration for Oracle that ships with
+ every release in:
+ <br />
+ /webapps/openmeetings/WEB-INF/classes/META-INF/oracle_persistence.xml
+ </p>
+ </subsection>
+
+
+ </section>
+
+ </body>
+
+</document>
Added: incubator/openmeetings/trunk/singlewebapp/xdocs/PostgresConfig.xml
URL: http://svn.apache.org/viewvc/incubator/openmeetings/trunk/singlewebapp/xdocs/PostgresConfig.xml?rev=1220385&view=auto
==============================================================================
--- incubator/openmeetings/trunk/singlewebapp/xdocs/PostgresConfig.xml (added)
+++ incubator/openmeetings/trunk/singlewebapp/xdocs/PostgresConfig.xml Sun Dec 18 12:42:23 2011
@@ -0,0 +1,82 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+
+<!-- Copyright 2006 The Apache Software Foundation Licensed under the Apache
+ License, Version 2.0 (the "License"); you may not use this file except in
+ compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0
+ Unless required by applicable law or agreed to in writing, software distributed
+ under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES
+ OR CONDITIONS OF ANY KIND, either express or implied. See the License for
+ the specific language governing permissions and limitations under the License. -->
+
+
+<document>
+
+ <properties>
+ <title>Postgres Configuration</title>
+ <author email="sebawagner@incubator.apache.org">
+ Apache OpenMeetings Documentation Team
+ </author>
+ </properties>
+
+ <body>
+ <section name="Postgres Configuration">
+
+ <subsection name="Before you start">
+ <ul>
+ <li>Make sure that you have set utf8 as default/server-character-set
+ </li>
+ <li>
+ make sure Postgres is listening on TCP/IP connections!
+ <br />
+ To verify if Postgres connection is working: OpenMeetings will
+ automatically create all tables in the database and all tables
+ should have utf8 as encoding/collation!
+ </li>
+ <li>If you encounter issues, you can drop the db again and delete
+ the file $red5/webapps/openmeetings/conf/install.xml and then run
+ the web based installer again
+ </li>
+ </ul>
+ </subsection>
+
+ <subsection name="Steps todo">
+ <ul>
+ <li>
+ Rename:
+ <br />
+ $red5/webapps/openmeetings/WEB-INF/classes/META-INF/postgres_persistence.xml
+ <br />
+ to
+ <br />
+ $red5/webapps/openmeetings/WEB-INF/classes/META-INF/persistence.xml
+ </li>
+ <li>
+ Prepare Database Settings - go to
+ openmeetings_version_no_xx/webapps/openmeetings/WEB-INF/classes/META-INF/persistence.xml
+ <br />
+ Alter config values in persistence.xml DB_HOST USER_NAME USER_PASS
+ with your values
+ </li>
+ <li>
+ Run red5-service and goto the web-based installer:
+ http://localhost:5080/openmeetings/install
+ </li>
+ </ul>
+ </subsection>
+
+ <subsection name="Postgres Sample Configuration">
+ <p>
+ There is a sample configuration for Postgres that ships with
+ every
+ release in:
+ <br />
+ /webapps/openmeetings/WEB-INF/classes/META-INF/postgres_persistence.xml
+ </p>
+ </subsection>
+
+
+ </section>
+
+ </body>
+
+</document>
Added: incubator/openmeetings/trunk/singlewebapp/xdocs/images/ldap_screen.png
URL: http://svn.apache.org/viewvc/incubator/openmeetings/trunk/singlewebapp/xdocs/images/ldap_screen.png?rev=1220385&view=auto
==============================================================================
Binary file - no diff available.
Propchange: incubator/openmeetings/trunk/singlewebapp/xdocs/images/ldap_screen.png
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Modified: incubator/openmeetings/trunk/singlewebapp/xdocs/stylesheets/project.xml
URL: http://svn.apache.org/viewvc/incubator/openmeetings/trunk/singlewebapp/xdocs/stylesheets/project.xml?rev=1220385&r1=1220384&r2=1220385&view=diff
==============================================================================
--- incubator/openmeetings/trunk/singlewebapp/xdocs/stylesheets/project.xml (original)
+++ incubator/openmeetings/trunk/singlewebapp/xdocs/stylesheets/project.xml Sun Dec 18 12:42:23 2011
@@ -32,9 +32,20 @@
<item name="Dependencies" href="/dependencies.html"/>
</menu>
+ <menu name="Configuration">
+ <item name="DB Sample Configurations" >
+ <subitem name="Apache Derby" href="/ApacheDerbyConfig.html" />
+ <subitem name="IBM DB2" href="/IBMDB2Config.html" />
+ <subitem name="Oracle" href="/OracleConfig.html" />
+ <subitem name="MySQL" href="/MySQLConfig.html" />
+ <subitem name="Postgres" href="/PostgresConfig.html" />
+ </item>
+ </menu>
+
<menu name="Integration">
- <item name="SOAP/REST API" href="/SoapRestAPI.html"/>
- <item name="REST API Sample" href="/RestAPI.html"/>
+ <item name="SOAP/REST API" href="/SoapRestAPI.html" />
+ <item name="REST API Sample" href="/RestAPI.html" />
+ <item name="Ldap and ADS" href="/LdapAndADS.html" />
</menu>
<!--
Modified: incubator/openmeetings/trunk/singlewebapp/xdocs/stylesheets/site.vsl
URL: http://svn.apache.org/viewvc/incubator/openmeetings/trunk/singlewebapp/xdocs/stylesheets/site.vsl?rev=1220385&r1=1220384&r2=1220385&view=diff
==============================================================================
--- incubator/openmeetings/trunk/singlewebapp/xdocs/stylesheets/site.vsl (original)
+++ incubator/openmeetings/trunk/singlewebapp/xdocs/stylesheets/site.vsl Sun Dec 18 12:42:23 2011
@@ -254,9 +254,20 @@ limitations under the License.
<ul>
#foreach ( $item in $menu.getChildren() )
#set ($name = $item.getAttributeValue("name"))
- <font color="$menutablefg" face="arial,helvetica,sanserif" size="2pt">
- <li>#projectanchor($name $item.getAttributeValue("href"))</li>
- </font>
+ #if ( $item.getAttributeValue("href").length() > 0 )
+ <font color="$menutablefg" face="arial,helvetica,sanserif" size="2pt">
+ <li>#projectanchor($name $item.getAttributeValue("href"))</li>
+ </font>
+ #else
+ <li><font color="$menutablefg" face="arial,helvetica,sanserif" size="2pt">$name</font>
+ <ul>
+ #foreach ( $subitem in $item.getChildren() )
+ #set ($name = $subitem.getAttributeValue("name"))
+ <li>#projectanchor($name $subitem.getAttributeValue("href"))</li>
+ #end
+ </ul>
+ </li>
+ #end
#end
</ul>
</div>
Modified: incubator/openmeetings/trunk/singlewebapp/xdocs/svn.xml
URL: http://svn.apache.org/viewvc/incubator/openmeetings/trunk/singlewebapp/xdocs/svn.xml?rev=1220385&r1=1220384&r2=1220385&view=diff
==============================================================================
--- incubator/openmeetings/trunk/singlewebapp/xdocs/svn.xml (original)
+++ incubator/openmeetings/trunk/singlewebapp/xdocs/svn.xml Sun Dec 18 12:42:23 2011
@@ -1,287 +1,341 @@
<?xml version="1.0" encoding="ISO-8859-1"?>
-<!--
-
- Copyright 2006 The Apache Software Foundation
-
- Licensed under the Apache License, Version 2.0 (the "License");
- you may not use this file except in compliance with the License.
- You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing, software
- distributed under the License is distributed on an "AS IS" BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- See the License for the specific language governing permissions and
- limitations under the License.
--->
+<!-- Copyright 2006 The Apache Software Foundation Licensed under the Apache
+ License, Version 2.0 (the "License"); you may not use this file except in
+ compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0
+ Unless required by applicable law or agreed to in writing, software distributed
+ under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES
+ OR CONDITIONS OF ANY KIND, either express or implied. See the License for
+ the specific language governing permissions and limitations under the License. -->
<document>
-<properties>
-<title>Source Code</title>
-<author email="sebawagner@apache.org">
- Sebastian Wagner</author>
-</properties>
-
-<body>
-
-<section name="OpenMeetings Source Code">
-
-<p>OpenMeetings uses
-<a class="external" rel="nofollow" href="http://subversion.tigris.org">
-Subversion</a> to manage its source code.
-If you're new to Subversion, you can check out the
-<a href="http://svnbook.red-bean.com/">online book</a> about Subversion.
-Note that we are currently using Subversion 1.1.x (there are separate
-versions of the book covering 1.0 and 1.1).
-</p>
-<p>
-To receive notice of commits to the repository subscribe to
-<a href="mailto:openmeetings-commits@incubator.apache.org">
-openmeetings-commits@incubator.apache.org</a> by sending email to
-<a href="mailto:openmeetings-commits-subscribe@incubator.apache.org">
-openmeetings-commits-subscribe@incubator.apache.org</a>.
-</p>
-
-</section>
-
-<section name="Web Access to Subversion">
-
-<p>
-If you just want to browse the source code, you can use the
-<a class="external" rel="nofollow"
-href="http://svn.apache.org/viewcvs/incubator/openmeetings">
-ViewCVS web interface</a> to Subversion. This is current at all times.
-</p>
-
-</section>
-
-<section name="Checking Out Code Using Subversion">
-
-<p>Anyone can check code out of Subversion. You only need to specify a
-username and password to update the Subversion repository, and only
-OpenMeetings committers can do that.
-If you are a committer, are working from behind a firewall, or are
-connected to the internet through a proxy server, please see the sections
-below for more information.
-</p>
-
-<subsection name="Anonymous check out from Subversion">
-<p>Use a command like:</p>
-<pre>% svn checkout http://svn.apache.org/repos/asf/incubator/openmeetings </pre>
-<p>Once you have OpenMeetings checked out you can update the source
-by executing the following command from within the openmeetings directory. </p>
-<pre>
-% svn update
-</pre>
-</subsection>
-<subsection name="Access from behind a firewall">
-
-<p>For those users who are stuck behind a corporate firewall which is
-blocking http access to the Subversion repository, you can try to access it
-via HTTPS: </p>
-<pre>
-% svn checkout https://svn.apache.org/repos/asf/incubator/openmeetings
-</pre>
-
-</subsection>
-<subsection name="Access through a proxy">
-
-<p>The Subversion client can go through a proxy, if you configure it
-to do so. First, edit your "servers" configuration file to indicate which
-proxy to use. The files location depends on your operating system.
-On Linux or Unix it is located in the directory "~/.subversion".
-On Windows it is in "%APPDATA%\Subversion". (Try "echo %APPDATA%",
-note this is a hidden directory.) </p>
-<p>There are comments in the file explaining what to do. If you don't have
-that file, get the latest Subversion client and run any command; this will
-cause the configuration directory and template files to be created.
-</p>
-<p>Example : Edit the 'servers' file and add something like :
-</p>
-<pre>
-[global]
-http-proxy-host = your.proxy.name
-http-proxy-port = 3128
-</pre>
-
-</subsection>
-
-<subsection name="Committer access">
-
-<p>Everyone can access the Apache Podling Subversion repository via HTTPS,
-but OpenMeetings Committers must checkout the Subversion repository
-via HTTPS.
-</p>
-<pre>
-% svn checkout https://svn.apache.org/repos/asf/incubator/openmeetings
-</pre>
-</subsection>
-</section>
-
-<section name="Submitting Code Changes">
-<subsection name="Submitting a patch">
-
-<p>If you make changes to OpenMeetings, and would like to contribute
-it to the project, you should open a JIRA issue and discuss the merits
-of the proposal with the developer community. If there is agreement,
-create a patch and attach it to the JIRA issue.
-</p>
-<p>
-To create a patch, execute the svn diff command. This creates a patch that
-can easily be uploaded to a JIRA issue. A good name for the patch includes
-the JIRA issue name, e.g. OPENMEETINGS-104.patch. If there are several patches
-for the same JIRA issue, you might include your initials, e.g.
-OPENMEETINGS-104.clr.patch
-</p>
-<pre>
-% svn diff > OPENMEETINGS-104.clr.patch
-</pre>
-</subsection>
-
-<subsection name="Committing changes to subversion">
-<p>
-To commit changes to the subversion repository, you must be an
-OpenMeetings committer. See <a href="get-involved.html">get involved</a>
-for information on how to become a committer and how to set up your
-password once you become a committer.
-</p>
-
-<p>
-Once your password is set, you can use a command like this to commit:
-</p>
-<pre>
-$> svn commit --username your-username
-Authentication realm: <https://svn.apache.org:443> ASF Committers
-Password for 'your-username': your-password
-</pre>
-<p>You can also pass your password on the command line directly, but
-this is a security problem on multiuser unix computers (the command line
-arguments are available via the ps command). Here is the command if you
-are Windows or a single user unix computer:
-</p>
-<pre>
-$> svn commit --username your-username --password your-password
-</pre>
-<p>Remember to replace 'your-username' and 'your-password' with
-your actual username and password on svn.apache.org.
-</p>
-
-</subsection>
-</section>
-
-<section name="Building Podling from Source">
-<p>
-<!-- ***************** TBD ************************** -->
-<!-- ***************** TBD ************************** -->
-<!-- ***************** TBD ************************** -->
-<!-- ***************** TBD ************************** -->
-<!-- ***************** TBD ************************** -->
-<!-- ***************** TBD ************************** -->
-<!-- ***************** TBD ************************** -->
-</p>
-
-</section>
-
-<section name="Using Subversion on Windows with cygwin">
-
-<p>If you use Subversion on Windows under cygwin, you may find that the
-Subversion client automatically assigns the executable property to
-non-executable files. In that case, you would see this at the bottom of
-an <em>svn diff</em> of the file:
-</p>
-<pre>
-Property changes on: test/sql/derby/datastoreidentity/schema1.sql
-___________________________________________________________________
-Name: svn:executable
- + *
-</pre>
-<p>This section explains the source of the problem and suggests some
-actions to avoid it.
-</p>
-
-<subsection name="Background">
-
-<p>Subversion carries executable information in the built-in property
-called svn:executable. This property, unlike others, may be present
-or absent, but it has no value. You can add it or delete it, but you
-cannot change its value.
-</p>
-<p>In theory, Subversion ignores Windows file permissions and by default
-does not set svn:executable. However, cygwin svn acts like Unix svn and
-determines the svn:executable property based on file permissions.
-</p>
-<p>If you create a file from the cygwin command line, by default it is
-executable only if the filename ends with .bat, .com or .exe, or if its
-content starts with #!. [This is what the doc says, but you may see -x
-for all files.] If you create a file using a Windows tool, by default
-its Windows permissions are executable by all. Cygwin interprets the
-Unix-style permissions this way as well. If the file is executable by all,
-cygwin svn sets the svn:executable property on the file when you invoke
-<em>svn add</em>.
-</p>
-</subsection>
-<subsection name="Removing existing executable properties from the repository">
-
-<p>You can use svn propdel to remove the svn:executable property from your
-working copy.
-</p>
-<pre>
- svn propdel -R svn:executable .
-</pre>
-<p>will recursively remove the svn:executable property from all of the
-files below the current directory. You can use this and commit the
-files to clean the repository if necessary.
-</p>
-
-</subsection>
-<subsection name="Preventing Subversion from adding unwanted executable
+ <properties>
+ <title>Source Code</title>
+ <author email="sebawagner@apache.org">
+ Sebastian Wagner
+ </author>
+ </properties>
+
+ <body>
+
+ <section name="OpenMeetings Source Code">
+
+ <p>
+ OpenMeetings uses
+ <a class="external" rel="nofollow" href="http://subversion.tigris.org">
+ Subversion
+ </a>
+ to manage its source code.
+ If you're new to Subversion, you can check out the
+ <a href="http://svnbook.red-bean.com/">online book</a>
+ about Subversion.
+ Note that we are currently using Subversion 1.1.x (there are separate
+ versions of the book covering 1.0 and 1.1).
+ </p>
+ <p>
+ To receive notice of commits to the repository subscribe to
+ <a href="mailto:openmeetings-commits@incubator.apache.org">
+ openmeetings-commits@incubator.apache.org
+ </a>
+ by sending email to
+ <a href="mailto:openmeetings-commits-subscribe@incubator.apache.org">
+ openmeetings-commits-subscribe@incubator.apache.org
+ </a>
+ .
+ </p>
+
+ </section>
+
+ <section name="Web Access to Subversion">
+
+ <p>
+ If you just want to browse the source code, you can use the
+ <a class="external" rel="nofollow"
+ href="http://svn.apache.org/viewcvs/incubator/openmeetings">
+ ViewCVS web interface
+ </a>
+ to Subversion. This is current at all times.
+ </p>
+
+ </section>
+
+ <section name="Checking Out Code Using Subversion">
+
+ <p>Anyone can check code out of Subversion. You only need to specify
+ a
+ username and password to update the Subversion repository, and only
+ OpenMeetings committers can do that.
+ If you are a committer, are working from behind a firewall, or are
+ connected to the internet through a proxy server, please see the
+ sections
+ below for more information.
+ </p>
+
+ <subsection name="Anonymous check out from Subversion">
+ <p>Use a command like:</p>
+ <pre>% svn checkout
+ http://svn.apache.org/repos/asf/incubator/openmeetings </pre>
+ <p>Once you have OpenMeetings checked out you can update the source
+ by executing the following command from within the openmeetings
+ directory.
+ </p>
+ <pre>
+ % svn update
+ </pre>
+ </subsection>
+ <subsection name="Access from behind a firewall">
+
+ <p>For those users who are stuck behind a corporate firewall which
+ is
+ blocking http access to the Subversion repository, you can try to access it
+ via HTTPS:
+ </p>
+ <pre>
+ % svn checkout
+ https://svn.apache.org/repos/asf/incubator/openmeetings
+ </pre>
+
+ </subsection>
+ <subsection name="Access through a proxy">
+
+ <p>The Subversion client can go through a proxy, if you configure it
+ to do so. First, edit your "servers" configuration file to indicate
+ which
+ proxy to use. The files location depends on your operating system.
+ On Linux or Unix it is located in the directory "~/.subversion".
+ On Windows it is in "%APPDATA%\Subversion". (Try "echo %APPDATA%",
+ note this is a hidden directory.)
+ </p>
+ <p>There are comments in the file explaining what to do. If you
+ don't have
+ that file, get the latest Subversion client and run any command; this
+ will
+ cause the configuration directory and template files to be created.
+ </p>
+ <p>Example : Edit the 'servers' file and add something like :
+ </p>
+ <pre>
+ [global]
+ http-proxy-host = your.proxy.name
+ http-proxy-port = 3128
+ </pre>
+
+ </subsection>
+
+ <subsection name="Committer access">
+
+ <p>Everyone can access the Apache Podling Subversion repository via
+ HTTPS,
+ but OpenMeetings Committers must checkout the Subversion repository
+ via HTTPS.
+ </p>
+ <pre>
+ % svn checkout
+ https://svn.apache.org/repos/asf/incubator/openmeetings
+ </pre>
+ </subsection>
+ </section>
+
+ <section name="Submitting Code Changes">
+ <subsection name="Submitting a patch">
+
+ <p>If you make changes to OpenMeetings, and would like to contribute
+ it to the project, you should open a JIRA issue and discuss the
+ merits
+ of the proposal with the developer community. If there is agreement,
+ create a patch and attach it to the JIRA issue.
+ </p>
+ <p>
+ To create a patch, execute the svn diff command. This creates a patch
+ that
+ can easily be uploaded to a JIRA issue. A good name for the patch
+ includes
+ the JIRA issue name, e.g. OPENMEETINGS-104.patch. If there are several
+ patches
+ for the same JIRA issue, you might include your initials, e.g.
+ OPENMEETINGS-104.clr.patch
+ </p>
+ <pre>
+ % svn diff > OPENMEETINGS-104.clr.patch
+ </pre>
+ </subsection>
+
+ <subsection name="Committing changes to subversion">
+ <p>
+ To commit changes to the subversion repository, you must be an
+ OpenMeetings committer. See
+ <a href="get-involved.html">get involved</a>
+ for information on how to become a committer and how to set up your
+ password once you become a committer.
+ </p>
+
+ <p>
+ Once your password is set, you can use a command like this to commit:
+ </p>
+ <pre>
+ $> svn commit --username your-username
+ Authentication realm: <https://svn.apache.org:443> ASF Committers
+ Password for 'your-username': your-password
+ </pre>
+ <p>You can also pass your password on the command line directly, but
+ this is a security problem on multiuser unix computers (the command
+ line
+ arguments are available via the ps command). Here is the command if you
+ are Windows or a single user unix computer:
+ </p>
+ <pre>
+ $> svn commit --username your-username --password your-password
+ </pre>
+ <p>Remember to replace 'your-username' and 'your-password' with
+ your actual username and password on svn.apache.org.
+ </p>
+
+ </subsection>
+ </section>
+
+ <section name="Building Podling from Source">
+ <p>
+ <!-- ***************** TBD ************************** -->
+ <!-- ***************** TBD ************************** -->
+ <!-- ***************** TBD ************************** -->
+ <!-- ***************** TBD ************************** -->
+ <!-- ***************** TBD ************************** -->
+ <!-- ***************** TBD ************************** -->
+ <!-- ***************** TBD ************************** -->
+ </p>
+
+ </section>
+
+ <section name="Using Subversion on Windows with cygwin">
+
+ <p>
+ If you use Subversion on Windows under cygwin, you may find that the
+ Subversion client automatically assigns the executable property to
+ non-executable files. In that case, you would see this at the bottom
+ of
+ an
+ <em>svn diff</em>
+ of the file:
+ </p>
+ <pre>
+ Property changes on: test/sql/derby/datastoreidentity/schema1.sql
+ ___________________________________________________________________
+ Name: svn:executable
+ + *
+ </pre>
+ <p>This section explains the source of the problem and suggests some
+ actions to avoid it.
+ </p>
+
+ <subsection name="Background">
+
+ <p>Subversion carries executable information in the built-in
+ property
+ called svn:executable. This property, unlike others, may be present
+ or absent, but it has no value. You can add it or delete it, but you
+ cannot change its value.
+ </p>
+ <p>In theory, Subversion ignores Windows file permissions and by
+ default
+ does not set svn:executable. However, cygwin svn acts like Unix svn and
+ determines the svn:executable property based on file permissions.
+ </p>
+ <p>
+ If you create a file from the cygwin command line, by default it is
+ executable only if the filename ends with .bat, .com or .exe, or if
+ its
+ content starts with #!. [This is what the doc says, but you may see -x
+ for all files.] If you create a file using a Windows tool, by default
+ its Windows permissions are executable by all. Cygwin interprets
+ the
+ Unix-style permissions this way as well. If the file is executable by all,
+ cygwin svn sets the svn:executable property on the file when you
+ invoke
+ <em>svn add</em>
+ .
+ </p>
+ </subsection>
+ <subsection
+ name="Removing existing executable properties from the repository">
+
+ <p>You can use svn propdel to remove the svn:executable property
+ from your
+ working copy.
+ </p>
+ <pre>
+ svn propdel -R svn:executable .
+ </pre>
+ <p>will recursively remove the svn:executable property from all of
+ the
+ files below the current directory. You can use this and commit the
+ files to clean the repository if necessary.
+ </p>
+
+ </subsection>
+ <subsection
+ name="Preventing Subversion from adding unwanted executable
properties">
-<p>Windows/cygwin users who don't want to have to think about using <em>svn
-propdel</em> or <em>chmod</em> on each added file can use a non-cygwin
-version of svn. The Subversion 1.2.3 Win32 binaries, downloadable from the
-link at the bottom of <a rel="nofollow"
-href="http://subversion.tigris.org/project_packages.html">
-http://subversion.tigris.org/project_packages.html</a>, appear to work
-well. After installation add the svn.exe location to your Windows PATH
-variable. If you are switching from cygwin svn to Win32 svn </p>
-<ol type="1">
-<li>
-<p>Remove the subversion component from your cygwin installation
-because when svn is invoked from a cygwin window, the cygwin version is
-found even if your cygwin/bin directory is later on the path. (In the
-Select Packages window of the setup wizard, navigate to the subversion
-package in the Devel. category. Click on the status icon until Uninstall
-is displayed. Click next and continue through the wizard until installation
-is complete.)
-</p>
-</li>
-<li>
-<p>Copy the servers file and the auth folder from the sygwin ~/.subversion
-directory to C:\Documents and
-Settings\<user>\Application Data\Subversion used by Win32
-subversion.
-</p>
-</li>
-</ol>
-<p>Note that windows svn uses backslash as the path separator when
-displaying file names. You cannot just copy and paste this file name
-to another svn command when running from within a cygwin shell.
-You need to enclose the file name into double quotes.
-</p>
-<p>Alternatively, Windows users can set file permissions in Windows
-Explorer. (Right-click on the top-level folder & select Properties.
-Select the Security tab. Click Advanced. Remove all instances of
-Read & Execute from the Permission Entries. Click "Reset permissions
-on all child objects and enable propogations of inheritable permissions".
-Click Apply. OK. OK.) You will have to do this again when you do a clean
-checkout to a new directory.
-</p>
-
-</subsection>
-</section>
-</body>
+ <p>
+ Windows/cygwin users who don't want to have to think about using
+ <em>svn
+ propdel
+ </em>
+ or
+ <em>chmod</em>
+ on each added file can use a non-cygwin
+ version of svn. The Subversion 1.2.3 Win32 binaries, downloadable from the
+ link at the bottom of
+ <a rel="nofollow" href="http://subversion.tigris.org/project_packages.html">
+ http://subversion.tigris.org/project_packages.html
+ </a>
+ , appear to work
+ well. After installation add the svn.exe location to your Windows PATH
+ variable. If you are switching from cygwin svn to Win32 svn
+ </p>
+ <ol type="1">
+ <li>
+ <p>Remove the subversion component from your cygwin installation
+ because when svn is invoked from a cygwin window, the cygwin
+ version is
+ found even if your cygwin/bin directory is later on the path. (In the
+ Select Packages window of the setup wizard, navigate to the
+ subversion
+ package in the Devel. category. Click on the status icon until Uninstall
+ is displayed. Click next and continue through the wizard until
+ installation
+ is complete.)
+ </p>
+ </li>
+ <li>
+ <p>Copy the servers file and the auth folder from the sygwin
+ ~/.subversion
+ directory to C:\Documents and
+ Settings\<user>\Application Data\Subversion used by Win32
+ subversion.
+ </p>
+ </li>
+ </ol>
+ <p>Note that windows svn uses backslash as the path separator when
+ displaying file names. You cannot just copy and paste this file
+ name
+ to another svn command when running from within a cygwin shell.
+ You need to enclose the file name into double quotes.
+ </p>
+ <p>Alternatively, Windows users can set file permissions in Windows
+ Explorer. (Right-click on the top-level folder & select
+ Properties.
+ Select the Security tab. Click Advanced. Remove all instances of
+ Read & Execute from the Permission Entries. Click "Reset
+ permissions
+ on all child objects and enable propogations of inheritable
+ permissions".
+ Click Apply. OK. OK.) You will have to do this again when you do a clean
+ checkout to a new directory.
+ </p>
+
+ </subsection>
+ </section>
+ </body>
</document>