aries-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r960262 - in /websites/staging/aries/trunk/content: ./ development/buildingaries.html
Date Fri, 31 Jul 2015 08:27:09 GMT
Author: buildbot
Date: Fri Jul 31 08:27:08 2015
New Revision: 960262

Log:
Staging update by buildbot for aries

Modified:
    websites/staging/aries/trunk/content/   (props changed)
    websites/staging/aries/trunk/content/development/buildingaries.html

Propchange: websites/staging/aries/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Jul 31 08:27:08 2015
@@ -1 +1 @@
-1690692
+1693541

Modified: websites/staging/aries/trunk/content/development/buildingaries.html
==============================================================================
--- websites/staging/aries/trunk/content/development/buildingaries.html (original)
+++ websites/staging/aries/trunk/content/development/buildingaries.html Fri Jul 31 08:27:08
2015
@@ -98,7 +98,18 @@
                 <div id="wrapper-menu-page-bottom">
                   <div id="menu-page">
                     <!-- NavigationBar -->
-          <div onclick="SwitchMenu('overview')" id="overviewTitle" class="menutitle">Overview</div>
+          <style type="text/css">
+/* The following code is added by mdx_elementid.py
+   It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
> .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink
{ visibility: visible }</style>
+<div onclick="SwitchMenu('overview')" id="overviewTitle" class="menutitle">Overview</div>
 
 <div id="overview" class="menuitemgroup">
     <div class="menuitem">
@@ -281,123 +292,58 @@
           </td>
           <td height="100%" width="100%">
             <!-- Content -->
-            <div class="wiki-content"><p><a name="BuildingAries-ExtractingandbuildingAries"></a></p>
-<h1 id="extracting-and-building-aries">Extracting and building Aries</h1>
-<p>There are two ways to do this. The first avoids using the command line but
-can leave you with some fixing up to do on the projects.</p>
+            <div class="wiki-content"><style type="text/css">
+/* The following code is added by mdx_elementid.py
+   It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
> .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink
{ visibility: visible }</style>
+<p><a name="BuildingAries-ExtractingandbuildingAries"></a></p>
 <p><a name="BuildingAries-Prereqs"></a></p>
-<h2 id="prereqs">Prereqs</h2>
+<h2 id="prereqs">Prereqs<a class="headerlink" href="#prereqs" title="Permanent link">&para;</a></h2>
 <ul>
-<li>Check that Maven is 2.0.10 or higher (mvn --version)</li>
-<li>Download and extract eclipse-jee-ganymede-SR2-linux-gtk.tar.gz (this is
-the 3.4 version)</li>
-<li>Install Subversion client http://subclipse.tigris.org/update_1.6.x (Just
-the Subclipse and Core)</li>
-<li>Install m2eclipse http://download.eclipse.org/technology/m2e/releases (Maven
-Integration and Maven optional components)</li>
+<li>Maven 3.2.5 (mvn --version). Current maven 3.3.x has an error with parent poms</li>
+<li>Subversion client &gt;= 1.8.x</li>
+<li>Eclipse Luna http://www.eclipse.org/downloads/packages/eclipse-ide-java-developers/lunasr2</li>
 </ul>
-<p><a name="BuildingAries-BuildatthecommandlinethenimportintoEclipseifyouneedEclipse."></a></p>
-<h2 id="build-at-the-command-line-then-import-into-eclipse-if-you-need-eclipse">Build
at the command line then import into Eclipse if you need Eclipse.</h2>
-<p>This is the easiest way to build Aries and then work on the modules using
-Eclipse. If you don't care about Eclipse go to the next section.</p>
+<p><a name="BuildingAries-CheckoutAndBuild"></a></p>
+<h2 id="checkout-and-build-on-the-command-line">Checkout and build on the command line<a
class="headerlink" href="#checkout-and-build-on-the-command-line" title="Permanent link">&para;</a></h2>
 <ul>
-<li>check out from the command line: svn co
-https://svn.apache.org/repos/asf/aries/trunk aries</li>
+<li>Check out sources: svn co https://svn.apache.org/repos/asf/aries/trunk aries</li>
 <li>cd aries</li>
-<li>cd parent</li>
-<li>mvn clean install</li>
-<li>cd ../eba-maven-plugin</li>
-<li>mvn clean install (<em>See note below</em>)</li>
-<li>cd ..</li>
-<li>mvn clean install</li>
-<li>mvn eclipse:eclipse (should see 'BUILD SUCCESSFUL' message)</li>
-<li>fire up eclipse and switch to the Java perspective</li>
-<li>import the projects. File-&gt;import-&gt;General-&gt;existing projects
into
-workspace. Import 'blueprint, 'jndi', 'testsupport' and 'transaction'</li>
+<li>mvn clean install -DskipTests=true</li>
 </ul>
-<p>If everything looks good run a  maven build with the target 'install' (adds
-jars to your local repository) or 'package' (just creates jars in your
-workspace). Hit F5 in the package explorer view to refresh and you should
-see packaged jar files under the <em>target</em> directories in the projects.</p>
-<p><br></p>
-<hr />
-<p><strong>Note:</strong>
-Note: There is currently (September 2010) what appears to be a timing issue
-that is causing unpredictable test failures during a full build. If you see
-test failures, try 'mvn install -fae'</p>
-<hr />
-<p><a name="BuildingAries-Justbuildit-noEclipse"></a></p>
-<h2 id="just-build-it-no-eclipse">Just build it - no Eclipse</h2>
+<p>You should now have succesfully compiled aries trunk.
+As a next step you can run the tests too.</p>
 <ul>
-<li>check out from the command line: svn co
-https://svn.apache.org/repos/asf/aries/trunk aries</li>
-<li>cd aries</li>
-<li>cd parent</li>
-<li>mvn clean install</li>
-<li>cd ../eba-maven-plugin</li>
-<li>mvn clean install</li>
-<li>cd ..</li>
-<li>mvn clean</li>
-<li><em>mvn -fn install</em> (-fn continues after failures), or {{mvn -fn
-package}} (alternatively, you can disable the tests with {{mvn
--Dmaven.test.skip=true install}} with the side-effect of making the build
-process much faster)</li>
+<li>mvn clean install -fae</li>
+</ul>
+<p><a name="BuildingAries-ImportIntoEclipse"></a></p>
+<h1 id="import-into-eclipse-using-m2e">Import into eclipse using m2e<a class="headerlink"
href="#import-into-eclipse-using-m2e" title="Permanent link">&para;</a></h1>
+<ul>
+<li>Start eclipse. Use a workspace directory separate from your source checkout of
aries</li>
+<li>File -&gt; Import -&gt; Maven -&gt; Existing maven projects -&gt;
Browse to aries directory -&gt; Select the projects to import -&gt; Finish</li>
+<li>At some projects you might see some markers that m2e does not know how to work
with certain maven plugins. Use the Ctrl-1 shortcut on these markers and set them to be ignored
and let eclipse store this in the eclipse preferences. Do not select to add the ignore to
the maven poms.</li>
 </ul>
-<p><a name="BuildingAries-Eclipseonly"></a></p>
-<h2 id="eclipse-only">Eclipse only</h2>
-<p>This should work if you are command-line averse. On the other hand it seems
-to be the best way to get into a mess with the M2Eclipse plugin.</p>
+<p>After these steps you should have imported your selected aries projects into eclipse.
</p>
+<p><a name="BuildingAries-CodeStyle"></a></p>
+<h1 id="code-styles">Code Styles<a class="headerlink" href="#code-styles" title="Permanent
link">&para;</a></h1>
+<p>There are not yet complete code formatters and checkstyle rules for aries. In the
mean time you can set these rules.</p>
 <ul>
-<li>In the SVN view, add the aries repository
-https://svn.apache.org/repos/asf/aries</li>
-<li>Expand the repository, right click on trunk and take 'check out as Maven
-project'
-There will be errors in the projects. To fix these:</li>
-<li>Right click on pom/xml in the aries project, select 'run as Maven
-build....'</li>
-<li>Type 'clean' in as the build goal</li>
-<li>Repeat the process using 'eclipse:eclipse' as the build goals'</li>
-<li>Close and re-open all the projects</li>
+<li>4 spaces instead of tabs</li>
+<li>Line width 130 characters</li>
 </ul>
-<p>If there are still failures see the "Fixing failures" step below. If
-everything looks good run a final maven build with the target 'install'
-(adds jars to your local repository) or 'package' (just creates jars in
-your workspace). Hit F5 in the package explorer view to refresh and you
-should see packaged jar files under the <em>target</em> directories in the
-projects.</p>
-<p><a name="BuildingAries-Fixingfailures"></a></p>
-<h2 id="fixing-failures">Fixing failures</h2>
-<p><a name="BuildingAries-InEclipse"></a></p>
-<h5 id="in-eclipse">In Eclipse</h5>
-<p>You will see some of the blueprint projects don't build. To fix this you
-need to comment out the following line:</p>
-<div class="codehilite"><pre><span class="o">&lt;</span>!<span
class="o">--</span> <span class="o">&lt;</span><span class="n">classpathentry</span>
<span class="n">kind</span><span class="p">=</span>&quot;<span
class="n">src</span>&quot;
-<span class="n">path</span><span class="p">=</span>&quot;<span
class="o">/</span><span class="n">Users</span><span class="o">/</span><span
class="n">linsun</span><span class="o">/</span><span class="n">aries</span><span
class="o">/</span><span class="n">blueprint</span><span class="o">/</span><span
class="n">blueprint</span><span class="o">-</span><span class="n">api</span><span
class="o">/</span><span class="n">src</span><span class="o">/</span><span
class="n">main</span><span class="o">/</span><span class="n">resources</span><span
class="o">/</span><span class="n">org</span><span class="o">/</span><span
class="n">osgi</span><span class="o">/</span><span class="n">service</span><span
class="o">/</span><span class="n">blueprint</span>&quot;
-<span class="n">including</span><span class="p">=</span>&quot;<span
class="n">blueprint</span><span class="p">.</span><span class="n">xsd</span>&quot;
<span class="n">excluding</span><span class="p">=</span>&quot;<span
class="o">**/*</span><span class="p">.</span><span class="n">java</span>&quot;<span
class="o">/&gt;</span> <span class="o">--&gt;</span>
-</pre></div>
-
-
-<p>in the .classpath file in the aries-blueprint-core project.</p>
-<p>If there is a build error in the org.apache.aries.blueprint.itests project
-then remove this jar:</p>
-<div class="codehilite"><pre><span class="n">org</span><span class="o">/</span><span
class="n">apache</span><span class="o">/</span><span class="n">felix</span><span
class="o">/</span><span class="n">org</span><span class="p">.</span><span
class="n">osgi</span><span class="p">.</span><span class="n">foundation</span><span
class="o">/</span>1<span class="p">.</span>2<span class="p">.</span>0<span
class="p">.</span><span class="n">jar</span>
-</pre></div>
-
-
-<p>from the project's classpath.</p>
-<p>If there is a build error in the aries-jmx-core project then configure this
-project's build path to add the JRE System Library to Java Build Path.</p>
-<p>There should be no outstanding errors.</p>
 <p><a name="BuildingAries-Outofmemoryerrors"></a></p>
-<h5 id="out-of-memory-errors">Out of memory errors</h5>
+<h5 id="out-of-memory-errors">Out of memory errors<a class="headerlink" href="#out-of-memory-errors"
title="Permanent link">&para;</a></h5>
 <p>You may find that building Aries fails with out of memory exceptions on
 some systems (eg Mac)  if you use the standard Java settings. Setting the
 two environment variables as shown below may help.</p>
-<div class="codehilite"><pre><span class="n">export</span> <span
class="n">MAVEN_OPTS</span><span class="p">=</span>&quot;<span
class="o">-</span><span class="n">XX</span><span class="p">:</span><span
class="n">MaxPermSize</span><span class="p">=</span>128<span class="n">m</span>
<span class="o">-</span><span class="n">Xms512m</span> <span class="o">-</span><span
class="n">Xmx512m</span>
-<span class="o">-</span><span class="n">XX</span><span class="p">:</span><span
class="o">+</span><span class="n">HeapDumpOnOutOfMemoryError</span>&quot;
-<span class="n">export</span> <span class="n">JAVA_OPTS</span><span
class="p">=</span>&quot;<span class="o">-</span><span class="n">Xmx1024m</span>
<span class="o">-</span><span class="n">XX</span><span class="p">:</span><span
class="n">MaxPermSize</span><span class="p">=</span>128<span class="n">m</span>
-<span class="o">-</span><span class="n">XX</span><span class="p">:</span><span
class="o">+</span><span class="n">HeapDumpOnOutOfMemoryError</span>&quot;
-</pre></div></div>
+<p>export MAVEN_OPTS="-XX:MaxPermSize=128m -Xms512m -Xmx512m"</p></div>
             <!-- Content -->
           </td>
         </tr>



Mime
View raw message