Author: buildbot
Date: Tue Sep 22 13:56:59 2015
New Revision: 966354

Log:
Staging update by buildbot for slider

Modified:
    websites/staging/slider/trunk/content/   (props changed)
    websites/staging/slider/trunk/content/developing/building.html

Propchange: websites/staging/slider/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Sep 22 13:56:59 2015
@@ -1 +1 @@
-1692951
+1704630

Modified: websites/staging/slider/trunk/content/developing/building.html
==============================================================================
--- websites/staging/slider/trunk/content/developing/building.html (original)
+++ websites/staging/slider/trunk/content/developing/building.html Tue Sep 22 
13:56:59 2015
@@ -168,7 +168,18 @@ Latest release: <strong>0.80.0-incubatin
 
     <h1 class="title"></h1>
 
-    <!---
+    <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>
+<!---
    Licensed to the Apache Software Foundation (ASF) under one or more
    contributor license agreements.  See the NOTICE file distributed with
    this work for additional information regarding copyright ownership.
@@ -185,18 +196,18 @@ Latest release: <strong>0.80.0-incubatin
    limitations under the License.
 -->
 
-<h1 id="building-apache-slider">Building Apache Slider</h1>
+<h1 id="building-apache-slider">Building Apache Slider<a class="headerlink" 
href="#building-apache-slider" title="Permanent link">&para;</a></h1>
 <p>Here's how to set this up.</p>
-<h2 id="before-you-begin">Before you begin</h2>
-<h3 id="networking">Networking</h3>
+<h2 id="before-you-begin">Before you begin<a class="headerlink" 
href="#before-you-begin" title="Permanent link">&para;</a></h2>
+<h3 id="networking">Networking<a class="headerlink" href="#networking" 
title="Permanent link">&para;</a></h3>
 <p>The network on the development system must be functional, with hostname 
lookup
 of the local host working. Tests will fail without this. For maven builds to
 work, remote network access is often a pre-requisite.</p>
-<h3 id="java">Java</h3>
+<h3 id="java">Java<a class="headerlink" href="#java" title="Permanent 
link">&para;</a></h3>
 <p>Slider is built on Java 6 or later.</p>
-<h3 id="python">Python</h3>
+<h3 id="python">Python<a class="headerlink" href="#python" title="Permanent 
link">&para;</a></h3>
 <p>Slider requires python 2.6</p>
-<h3 id="maven">Maven</h3>
+<h3 id="maven">Maven<a class="headerlink" href="#maven" title="Permanent 
link">&para;</a></h3>
 <p>You will need a version of Maven 3.0+, set up with enough memory</p>
 <div class="codehilite"><pre><span class="n">MAVEN_OPTS</span><span 
class="p">=</span><span class="o">-</span><span class="n">Xms256m</span> <span 
class="o">-</span><span class="n">Xmx512m</span> <span class="o">-</span><span 
class="n">Djava</span><span class="p">.</span><span class="n">awt</span><span 
class="p">.</span><span class="n">headless</span><span class="p">=</span><span 
class="n">true</span>
 </pre></div>
@@ -204,7 +215,7 @@ work, remote network access is often a p
 
 <p><em>Important</em>: As of December 2014, Maven 3.1 is not supported due to
 <a 
href="https://cwiki.apache.org/confluence/display/MAVEN/AetherClassNotFound";>version
 issues</a>.</p>
-<h3 id="protoc">Protoc</h3>
+<h3 id="protoc">Protoc<a class="headerlink" href="#protoc" title="Permanent 
link">&para;</a></h3>
 <p>You need a copy of the <code>protoc</code> compiler for protobuf 
compilation</p>
 <ol>
 <li>OS/X: <code>brew install protobuf</code></li>
@@ -212,10 +223,10 @@ work, remote network access is often a p
 </ol>
 <p>The version of <code>protoc</code> installed must be the same as that used 
by Hadoop itself.
 This is absolutely critical to prevent JAR version problems.</p>
-<h3 id="obtain-the-source-code">Obtain the source code</h3>
+<h3 id="obtain-the-source-code">Obtain the source code<a class="headerlink" 
href="#obtain-the-source-code" title="Permanent link">&para;</a></h3>
 <p>Download the source tarball for the release to be build. Alternatively, you 
can clone the Slider git repo.</p>
-<p><code>git clone 
https://git-wip-us.apache.org/repos/asf/incubator-slider.git</code></p>
-<h3 id="build-install-and-run-unit-tests">Build, install and run unit 
tests</h3>
+<p><code>git clone 
https://git-wip-us.apache.org/repos/asf/incubator-slider.git -b 
develop</code></p>
+<h3 id="build-install-and-run-unit-tests">Build, install and run unit tests<a 
class="headerlink" href="#build-install-and-run-unit-tests" title="Permanent 
link">&para;</a></h3>
 <div class="codehilite"><pre> <span class="n">mvn</span> <span 
class="n">clean</span> <span class="n">install</span>
 </pre></div>
 
@@ -224,7 +235,7 @@ This is absolutely critical to prevent J
 By default functional tests are not run as these tests are developed to be run
 against live hadoop clusters and require some manual setup. 
 You can run them based as described at <a 
href="/developing/functional_tests.html">functional test</a>.     </p>
-<h3 id="create-slider-package">Create Slider Package</h3>
+<h3 id="create-slider-package">Create Slider Package<a class="headerlink" 
href="#create-slider-package" title="Permanent link">&para;</a></h3>
 <div class="codehilite"><pre> <span class="n">mvn</span> <span 
class="n">clean</span> <span class="n">site</span><span class="p">:</span><span 
class="n">site</span> <span class="n">site</span><span class="p">:</span><span 
class="n">stage</span> <span class="n">package</span> <span 
class="o">-</span><span class="n">DskipTests</span>
 </pre></div>
 
@@ -233,7 +244,7 @@ You can run them based as described at <
 The build instructions below are optional and are proven to
 be useful when debugging deep into the hadoop code base.</em></strong></p>
 <hr />
-<h2 id="building-a-compatible-hadoop-version">Building a compatible Hadoop 
version</h2>
+<h2 id="building-a-compatible-hadoop-version">Building a compatible Hadoop 
version<a class="headerlink" href="#building-a-compatible-hadoop-version" 
title="Permanent link">&para;</a></h2>
 <p>Slider is built against Hadoop 2 -you can download and install
 a copy from the <a href="http://hadoop.apache.org";>Apache Hadoop Web 
Site</a>.</p>
 <p>During development, its convenient (but not mandatory)
@@ -283,7 +294,7 @@ a branch off it:)</p>
 <p>This creates an expanded version of Hadoop. You can now actually run Hadoop
 from this directory. Do note that unless you have the native code built for
 your target platform, Hadoop will be slower. </p>
-<h2 id="building-a-compatible-hbase-version">Building a compatible HBase 
version</h2>
+<h2 id="building-a-compatible-hbase-version">Building a compatible HBase 
version<a class="headerlink" href="#building-a-compatible-hbase-version" 
title="Permanent link">&para;</a></h2>
 <p>If you need to build a version of HBase -rather than use a released version,
 here are the instructions (for the hbase-0.98 release branch)</p>
 <p>Checkout the HBase <code>trunk</code> branch from apache svn/github.  </p>
@@ -351,7 +362,7 @@ see <a href="http://hbase.apache.org/boo
 </pre></div>
 
 
-<h2 id="building-accumulo">Building Accumulo</h2>
+<h2 id="building-accumulo">Building Accumulo<a class="headerlink" 
href="#building-accumulo" title="Permanent link">&para;</a></h2>
 <p>Clone accumulo from apache;</p>
 <div class="codehilite"><pre><span class="n">git</span> <span 
class="n">clone</span> <span class="n">http</span><span class="p">:</span><span 
class="o">//</span><span class="n">git</span><span class="o">-</span><span 
class="n">wip</span><span class="o">-</span><span class="n">us</span><span 
class="p">.</span><span class="n">apache</span><span class="p">.</span><span 
class="n">org</span><span class="o">/</span><span class="n">repos</span><span 
class="o">/</span><span class="n">asf</span><span class="o">/</span><span 
class="n">accumulo</span><span class="p">.</span><span class="n">git</span>
 </pre></div>
@@ -394,7 +405,7 @@ to create an expanded directory</p>
 <p>Note that the final location of the accumulo files is needed for the 
configuration,
 it may be directly under target/ or it may be in a subdirectory, with
 a path such as 
<code>target/accumulo-$ACCUMULO_VERSION-dev/accumulo-$ACCUMULO_VERSION/</code></p>
-<h2 id="building-the-slider-rpm">Building the Slider RPM</h2>
+<h2 id="building-the-slider-rpm">Building the Slider RPM<a class="headerlink" 
href="#building-the-slider-rpm" title="Permanent link">&para;</a></h2>
 <p>It is possible to build an RPM file for slider. This is an architecture
 independent RPM with the artifacts  and layout of the slider .tar file, but 
hosted
 under <code>/usr/lib/slider</code>.</p>
@@ -430,7 +441,7 @@ to the target cluster.</li>
 </ol>
 </li>
 </ol>
-<h3 id="example">Example</h3>
+<h3 id="example">Example<a class="headerlink" href="#example" title="Permanent 
link">&para;</a></h3>
 <div class="codehilite"><pre><span class="c"># rpm -Uvh 
slider-0.31.0-incubating_SNAPSHOT20140709153353.noarch.rpm </span>
 <span class="n">Preparing</span><span class="p">...</span>                
<span class="c">########################################### [100%]</span>
    1<span class="p">:</span><span class="n">slider</span>                 
<span class="c">########################################### [100%]</span>
@@ -476,7 +487,7 @@ Address of <code>/0.0.0.0:8032</code> is
 </pre></div>
 
 
-<h3 id="rpm-configuration-files">RPM Configuration files</h3>
+<h3 id="rpm-configuration-files">RPM Configuration files<a class="headerlink" 
href="#rpm-configuration-files" title="Permanent link">&para;</a></h3>
 <p>The configuration directory of slider is chosen when the RPM is built. It 
is fixed
 in <code>slider-assembly/pom.xml</code> to  <code>src/conf-hdp</code></p>
 <div class="codehilite"><pre><span 
class="nt">&lt;src.confdir&gt;</span>src/conf-hdp<span 
class="nt">&lt;/src.confdir&gt;</span>
@@ -486,8 +497,8 @@ in <code>slider-assembly/pom.xml</code>
 <p>This configuration sets the <code>yarn.application.classpath</code> value 
to that required
 by HDP installations. To target other installations, alternate maven profiles
 will need to be defined.</p>
-<h2 id="testing">Testing</h2>
-<h2 id="debugging-a-failing-test">Debugging a failing test</h2>
+<h2 id="testing">Testing<a class="headerlink" href="#testing" title="Permanent 
link">&para;</a></h2>
+<h2 id="debugging-a-failing-test">Debugging a failing test<a 
class="headerlink" href="#debugging-a-failing-test" title="Permanent 
link">&para;</a></h2>
 <ol>
 <li>
 <p>Locate the directory <code>target/$TESTNAME</code> where TESTNAME is the 
name of the 
@@ -527,14 +538,14 @@ time, which is straightforward</p>
 </pre></div>
 
 
-<h3 id="building-the-jar-file">Building the JAR file</h3>
+<h3 id="building-the-jar-file">Building the JAR file<a class="headerlink" 
href="#building-the-jar-file" title="Permanent link">&para;</a></h3>
 <p>You can create the JAR file and set up its directories with</p>
 <div class="codehilite"><pre> <span class="n">mvn</span> <span 
class="n">package</span> <span class="o">-</span><span 
class="n">DskipTests</span>
 </pre></div>
 
 
-<h1 id="development-notes">Development Notes</h1>
-<h2 id="git-branch-model">Git branch model</h2>
+<h1 id="development-notes">Development Notes<a class="headerlink" 
href="#development-notes" title="Permanent link">&para;</a></h1>
+<h2 id="git-branch-model">Git branch model<a class="headerlink" 
href="#git-branch-model" title="Permanent link">&para;</a></h2>
 <p>The git branch model uses is
 <a href="http://nvie.com/posts/a-successful-git-branching-model/";>Git 
Flow</a>.</p>
 <p>This is a common workflow model for Git, and built in to
@@ -564,12 +575,12 @@ merge them back in when they are ready.<
 </pre></div>
 
 
-<h2 id="groovy">Groovy</h2>
+<h2 id="groovy">Groovy<a class="headerlink" href="#groovy" title="Permanent 
link">&para;</a></h2>
 <p>Slider uses Groovy 2.x as its language for writing tests —for better 
assertions
 and easier handling of lists and closures. The first prototype
 used Groovy on the production source, this was dropped in favor of
 a Java-only production codebase.</p>
-<h2 id="maven-utils">Maven utils</h2>
+<h2 id="maven-utils">Maven utils<a class="headerlink" href="#maven-utils" 
title="Permanent link">&para;</a></h2>
 <p>Here are some handy aliases to make maven easier </p>
 <div class="codehilite"><pre><span class="n">alias</span> <span 
class="n">mi</span><span class="p">=</span>&quot;<span class="n">mvn</span> 
<span class="n">install</span> <span class="o">-</span><span 
class="n">DskipTests</span>&quot;
 <span class="n">alias</span> <span class="n">mvi</span><span 
class="p">=</span>&quot;<span class="n">mvn</span> <span 
class="n">install</span> <span class="o">-</span><span 
class="n">DskipTests</span>&quot;


Reply via email to