You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@uima.apache.org by re...@apache.org on 2022/12/21 10:02:52 UTC
svn commit: r1906126 [3/3] - in /uima/site/trunk/uima-website: docs/ docs/d/ducc-v2-current/ docs/d/ruta-v2-current/ docs/d/uima-addons-2.3.1/ docs/d/uima-addons/ docs/d/uima-as-v2-current/ docs/d/uimafit-v2-current/ docs/d/uimaj-v2-current/ docs/image...
Modified: uima/site/trunk/uima-website/xdocs/svn.xml
URL: http://svn.apache.org/viewvc/uima/site/trunk/uima-website/xdocs/svn.xml?rev=1906126&r1=1906125&r2=1906126&view=diff
==============================================================================
--- uima/site/trunk/uima-website/xdocs/svn.xml (original)
+++ uima/site/trunk/uima-website/xdocs/svn.xml Wed Dec 21 10:02:50 2022
@@ -84,8 +84,6 @@ to manage its source code. uimaj, uimaF
<p>
The code for UIMA is stored in several repositories:</p>
<ol>
- <li>uimaj - the Java code for base UIMA</li>
- <li>uima-as - the Asynchronous Scaleout add-on for base UIMA</li>
<li>addons - a collection of add-ons for UIMA including annotators</li>
<li>sandbox - a collection of new things for UIMA, not yet released</li>
<li>uimacpp - the C++ framework supporting Annotators written in C++</li>
@@ -259,163 +257,5 @@ https://jira.atlassian.com/browse/SVN-37
</p>
</subsection>
</section>
-
-<!--
-<section name="Building UIMA">
-<subsection name="Building UIMA from Source" id="building.with.maven">
-<p>
- See <a href="building-uima.html">Building UIMA</a>.
-</p>
-
-<p>
- The source can be obtained in two ways:
- <ol><li>You can checkout the source from SVN, from trunk, or a particular tagged release, or</li>
- <li>you can use the source version of the release artifact you download from the download
- page.</li></ol>
-</p>
-
-</subsection>
-
-<subsection name="How to build the full Apache UIMA distribution" id="build.distribution">
-
- <p>Distributions include zip/tar packages of source or binaries.
- Please refer to <a href="distribution.html">Building a distribution</a> for
- details on how to do this.</p>
-
- <p>
- To build a distribution, first do a build as described in "Building from the command line".
- Then (assuming you set up the Eclipse path using one of the first 2 methods, execute the following:
-<longquote><pre>
-cd ../uimaj-distr
-mvn install
-</pre></longquote>
-</p>
-<p>
-This will build the javadocs, and will create
-.zip and .tar.gz archives of the full UIMA distribution in the <code>uimaj-distr/target</code>
-directory.
-
-</p>
-
-<p>Similarly, for building the uima-as add-on distribution, first be sure you've built
- the projects themselves (see above) and then do:
-<longquote><pre>
-cd ..\uima-as-distr
-mvn install
-</pre></longquote>
-</p>
-
-
-<p>Sandbox projects are built for distribution individually, by cd-ing to the individual
- sandbox project and running "mvn install". Note that this may not work on projects that
- are not advanced to the point where they are released - not all projects in the Sandbox are
- in a state where they are buildable.
-</p>
-
-</subsection>
-
-</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 noopener"
-href="https://subversion.tigris.org/project_packages.html">
-https://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>