You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@ace.apache.org by bu...@apache.org on 2013/04/23 15:13:19 UTC
svn commit: r859606 - in /websites/staging/ace/trunk/content: ./
dev-doc/getting-started.html
Author: buildbot
Date: Tue Apr 23 13:13:18 2013
New Revision: 859606
Log:
Staging update by buildbot for ace
Modified:
websites/staging/ace/trunk/content/ (props changed)
websites/staging/ace/trunk/content/dev-doc/getting-started.html
Propchange: websites/staging/ace/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Apr 23 13:13:18 2013
@@ -1 +1 @@
-1412800
+1470938
Modified: websites/staging/ace/trunk/content/dev-doc/getting-started.html
==============================================================================
--- websites/staging/ace/trunk/content/dev-doc/getting-started.html (original)
+++ websites/staging/ace/trunk/content/dev-doc/getting-started.html Tue Apr 23 13:13:18 2013
@@ -176,8 +176,9 @@
<p>There are two ways to obtain a copy of the source code. You can either download one of the source releases, or checkout the code from subversion.</p>
<h3 id="download-the-sources">Download the sources</h3>
<p>Point your browser to: http://ace.apache.org/download.html</p>
-<p>On that page you will find, amongst others, a link to the latest released sources. The page will automatically select a download mirror close to you. Download the archive and then type:</p>
-<div class="codehilite"><pre><span class="nv">$ </span>unzip apache-ace-src-1.0.0.zip
+<p>On that page you will find, amongst others, a link to the latest released sources, plus an archive containing all binary third-party dependencies. The page will automatically select a download mirror close to you. Download both the source and dependencies archive and then type:</p>
+<div class="codehilite"><pre><span class="nv">$ </span>unzip apache-ace-1.0.0-src.zip
+<span class="nv">$ </span>unzip apache-ace-1.0.0-deps.zip
</pre></div>
@@ -186,7 +187,7 @@
</pre></div>
-<p>In both cases you end up with a copy of the source code in the apache-ace folder.</p>
+<p>In both cases you end up with a copy of the source code.</p>
<h2 id="building-the-sources">Building the sources</h2>
<p>There are two ways to build the sources. You can either run a command line build or use Eclipse with Bndtools to build everything. If you want to actively start developing, we strongly recommend you use Eclipse with Bndtools as this is by far the most convenient way to build and run Apache ACE within a development environment.</p>
<h3 id="eclipse-with-bndtools">Eclipse with Bndtools</h3>
@@ -217,11 +218,17 @@
<h5 id="coding-guidelines">Coding guidelines</h5>
<p>If you want to develop for ACE, you might want to import the code templates and formatter rules for ACE. The formatter can be found in the <code>etc</code> folder in subversion, and you can import it into Eclipse as your default formatter for this workspace.</p>
<h4 id="running-debugging">Running & debugging</h4>
-<p>One of the benefits of the migration to BndTools is that we can now directly run ACE from Eclipse with almost zero effort. In fact, it is even possible to directly debug or profile ACE from Eclipse.</p>
+<p>One of the benefits of the migration to BndTools is that we can now directly run ACE from Eclipse with almost zero effort. In fact, it is even possible to directly debug or profile ACE from Eclipse. All runnable projects start with "run-" and contain a ".bndrun" file.</p>
<h5 id="ace-server">ACE server</h5>
-<p>To run or debug the ACE server, you open up the "<tt>server.bndrun</tt>" file in the "run-server" project. This will present you with a view in which you can directly choose to run it (use "Run OSGi") or debug it (use "Debug OSGi"). Alternatively, you can right click on "server.bndrun" and choose either "Run As -> OSGi Run" or "Debug As -> OSGi Run".</p>
+<p>To run or debug the ACE server, you open up the "<tt>server.bndrun</tt>" file in the "run-server" project. This will present you with a view in which you can directly choose to run it (use "Run OSGi") or debug it (use "Debug OSGi"). Alternatively, you can right click on "server.bndrun" and choose either "Run As -> Bnd OSGi Run Launcher" or "Debug As -> Bnd OSGi Run Launcher".</p>
+<h5 id="ace-obr">ACE obr</h5>
+<p>To run or debug the ACE obr, you open up the "<tt>obr.bndrun</tt>" file in the "run-obr" project. This will present you with a view in which you can directly choose to run it (use "Run OSGi") or debug it (use "Debug OSGi"). Alternatively, you can right click on "obr.bndrun" and choose either "Run As -> Bnd OSGi Run Launcher" or "Debug As -> Bnd OSGi Run Launcher".</p>
+<h5 id="ace-client">ACE client</h5>
+<p>To run or debug the ACE client, you open up the "<tt>client.bndrun</tt>" file in the "run-client" project. This will present you with a view in which you can directly choose to run it (use "Run OSGi") or debug it (use "Debug OSGi"). Alternatively, you can right click on "client.bndrun" and choose either "Run As -> Bnd OSGi Run Launcher" or "Debug As -> Bnd OSGi Run Launcher".</p>
+<h5 id="ace-server-allinone">ACE server-allinone</h5>
+<p>To run or debug the "all in one" ACE server, you open up the "<tt>server-allinone.bndrun</tt>" file in the "run-server-allinone" project. This will present you with a view in which you can directly choose to run it (use "Run OSGi") or debug it (use "Debug OSGi"). Alternatively, you can right click on "server-allinone.bndrun" and choose either "Run As -> Bnd OSGi Run Launcher" or "Debug As -> Bnd OSGi Run Launcher".</p>
<h5 id="ace-target">ACE target</h5>
-<p>You can also directly run a target from Eclipse. Doing this is almost equal as running the ACE server described in the previous section. The only difference is that for running a target, you need to use the "<tt>target.bndrun</tt>" file from the "run-target" project.</p>
+<p>You can also directly run a target from Eclipse. Doing this is almost equal as running the ones described in the previous sections. The only difference is that for running a target, you need to use the "<tt>target.bndrun</tt>" file from the "run-target" project.</p>
<h5 id="unit-tests">Unit tests</h5>
<p>ACE uses TestNG for its unit tests. To run a single test or a package of tests, use "Run As -> TestNG Test" or "Debug As -> TestNG Test". </p>
<h5 id="integration-tests">Integration tests</h5>