gump-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From kkoli...@apache.org
Subject svn commit: r1740366 - in /gump/site: index.html metadata/builder.html
Date Thu, 21 Apr 2016 17:30:46 GMT
Author: kkolinko
Date: Thu Apr 21 17:30:46 2016
New Revision: 1740366

URL: http://svn.apache.org/viewvc?rev=1740366&view=rev
Log:
Regenerate the site using Apache Forrest 0.9

Modified:
    gump/site/index.html
    gump/site/metadata/builder.html

Modified: gump/site/index.html
URL: http://svn.apache.org/viewvc/gump/site/index.html?rev=1740366&r1=1740365&r2=1740366&view=diff
==============================================================================
--- gump/site/index.html (original)
+++ gump/site/index.html Thu Apr 21 17:30:46 2016
@@ -207,8 +207,8 @@ document.write("Last Published: " + docu
 The Apache Gump continuous integration tool was the first one
 developed at
 the <a target="_blank" href="http://www.apache.org/">Apache Software Foundation</a>.
It is written in Python and fully supports Apache Ant, 
-Apache Maven (1.x to 3.x) and other build tools. Gump is unique in that it builds and compiles
software against 
-the latest development versions of those projects. This allows gump to detect potentially

+Apache Maven (1.x to 3.x) and <a href="metadata/builder.html">other build tools</a>.
Gump is unique in that it builds and compiles software against 
+the latest development versions of those projects. This allows Gump to detect potentially

 incompatible changes to that software just a few hours after those changes are checked into
the 
 version control system. Notifications are sent to the project team as soon as such a change
is 
 detected, referencing more detailed reports available online.
@@ -225,7 +225,7 @@ Gump project maintains its own dedicated
 <h2 class="boxed">How does Gump work?</h2>
 <div class="section">
 <p>
-      With Gump, <a href="http://svn.apache.org/viewcvs/gump/project">
+      With Gump, <a href="http://svn.apache.org/viewcvs/gump/metadata/project">
       project</a> definitions are mapped from XML into in memory
       objects for processing. Scripts execute SCM update
       commands for every module which contains a project being built, and
@@ -253,25 +253,30 @@ Gump project maintains its own dedicated
       and/or configure scripts.
     </p>
 <p>
-      In Ant's case
-    	Gump set's Ant's <a href="http://ant.apache.org/manual/sysclasspath.html">build.sysclasspath</a>
to <strong>only</strong> and manages the system classpath:<br>
-    	To quote Ant:<br>
+      For builds using Apache Ant,
+    	Gump sets <a href="http://ant.apache.org/manual/sysclasspath.html">build.sysclasspath</a>
property of Ant to <strong>only</strong> and manages the system classpath:<br>
+<br>
+    	To quote Ant manual:<br>
     	
 <em>Only the system classpath is used and classpaths specified in build files, etc
are ignored. 
-                This situation could be considered as the person running the build file knows
more about the environment than the person writing the build file</em>.<br>
-      Note that Gump uses the svn trunk version of Ant when building Ant projects.
+            This situation could be considered as the person running the build file knows
more about the environment than the person writing the build file</em>.<br>
+<br>
+      Note that Gump uses the lastest version of Ant (from tip of master branch in their
Git repository) when building Ant projects.
     </p>
 <p>
-      For Maven 1.x builds, Gump runs maven with the --offline switch
+      For Apache Maven 1.x builds, Gump runs Maven with the --offline switch
       and uses jar overrides.  Sometimes the artifact ids expected by
       maven and Gump's names of the jars don't match, in which case
       &lt;property&gt; elements have to be used to get the correct
       artifact ids.
     </p>
 <p>
-      So far Gump's support for Maven 2.x and later uses the most complex
-      approach, for the full story see <a href="metadata/builder.html#mvn2">the section
on the mvn2
-      builder</a>.  Support for Gradle hooks into the approach
+      So far Gump's support for Apache Maven 2.x and later uses the most complex
+      approach, using a proxy server. For the full story see <a href="metadata/builder.html#mvn2">the
section on the mvn2
+      builder</a>.
+    </p>
+<p>
+      Support for Gradle hooks into the approach
       taken for Maven and uses the same local repositories and
       repository proxy.
     </p>
@@ -281,8 +286,7 @@ Gump project maintains its own dedicated
       latest XML parser.
     </p>
 <p>
-      The results are captured into html pages that largely are consistent
-      with the style of the Jakarta project.  An extensive amount of hypertext
+      The results are captured into html pages. An extensive amount of hypertext
       links are added to allow quick and easy navigation, and failures are
       color coded on the main build page.
     </p>

Modified: gump/site/metadata/builder.html
URL: http://svn.apache.org/viewvc/gump/site/metadata/builder.html?rev=1740366&r1=1740365&r2=1740366&view=diff
==============================================================================
--- gump/site/metadata/builder.html (original)
+++ gump/site/metadata/builder.html Thu Apr 21 17:30:46 2016
@@ -156,9 +156,6 @@ document.write("Last Published: " + docu
 </ul>
 </li>
 <li>
-<a href="#script">script</a>
-</li>
-<li>
 <a href="#ant">ant</a>
 </li>
 <li>
@@ -177,23 +174,26 @@ document.write("Last Published: " + docu
 <a href="#mvn3install">mvn3install</a>
 </li>
 <li>
-<a href="#configure">configure</a>
+<a href="#gradle">gradle</a>
 </li>
 <li>
-<a href="#make">make</a>
+<a href="#script">script</a>
 </li>
 <li>
-<a href="#nant">nant</a>
+<a href="#configure">configure</a>
 </li>
 <li>
-<a href="#msbuild">msbuild</a>
+<a href="#make">make</a>
 </li>
 <li>
-<a href="#gradle">gradle</a>
+<a href="#nant">nant</a>
 </li>
 <li>
 <a href="#nuget">nuget</a>
 </li>
+<li>
+<a href="#msbuild">msbuild</a>
+</li>
 </ul>
 </div>
 </div>
@@ -514,62 +514,6 @@ document.write("Last Published: " + docu
 </div>
 
   
-<a name="script"></a>
-<h2 class="boxed">script</h2>
-<div class="section">
-<p>Specifies a script to be executed in order to make build a
-    project.</p>
-<p>The assumption is that the script can be invoked in a platform
-    independent manner, though the contents of the script may be
-    platform specific.  Specifically, if the name of the script is
-    "name" and no file with the name "name" exists in the project's
-    basedir, it will be invoked as follows:</p>
-<ul>
-      
-<li>On Windows/batch, "call .\name.bat"</li>
-      
-<li>On Unix/bash, "./name.sh"</li>
-    
-</ul>
-<table class="ForrestTable" cellspacing="1" cellpadding="4">
-      
-<tr>
-        
-<th colspan="1" rowspan="1">Attribute</th>
-        <th colspan="1" rowspan="1">Description</th>
-        <th colspan="1" rowspan="1">Required?</th>
-      
-</tr>
-      
-<tr>
-        
-<td colspan="1" rowspan="1">name</td>
-        <td colspan="1" rowspan="1">The name of the script to execute.</td>
-        <td colspan="1" rowspan="1">Yes</td>
-      
-</tr>
-    
-</table>
-<p>Additional command line arguments can be specified using nested
-    &lt;arg&gt; elements.  If the name of an arg start with "--" or
-    doesn't start with "-", then a single argument gets created from
-    one &lt;arg&gt; element, using "=" to join name and value.  If it
-    starts with a single "-", two arguments get created, one for the
-    name and one for the value.  For example:</p>
-<pre class="code">
-      &lt;script name="foo"&gt;
-        &lt;arg name="--double-dash" value="1"/&gt;
-        &lt;arg name="-single-dash" value="2"/&gt;
-        &lt;arg name="no-dash" value="3"/&gt;
-      &lt;/script&gt;
-    </pre>
-<p>becomes</p>
-<pre class="code">
-      ./foo --double-dash=1 -single-dash 2 no-dash=3
-    </pre>
-</div>
-
-  
 <a name="ant"></a>
 <h2 class="boxed">ant</h2>
 <div class="section">
@@ -909,18 +853,39 @@ document.write("Last Published: " + docu
 </div>
 
   
-<a name="configure"></a>
-<h2 class="boxed">configure</h2>
-<div class="section">
-<p>Is a specialized version of <a href="#script">script</a>
-    with the fixed script name of "configure".</p>
-</div>
-
-  
-<a name="make"></a>
-<h2 class="boxed">make</h2>
+<a name="gradle"></a>
+<h2 class="boxed">gradle</h2>
 <div class="section">
-<p>Specifies the arguments to be passed to make.</p>
+<p>
+<strong>The Gradle builder is a work in progress and may not be
+    working correctly.</strong>
+</p>
+<p>The <a target="_blank" href="http://gradle.org/">Gradle</a>
+    component of Gump (&lt;gradle&gt;) uses a
+    <strong>pre-installed</strong> version of <a target="_blank" href="http://gradle.org">Gradle</a>,
it does
+    <strong>NOT</strong> bootstrap Gradle itself.</p>
+<p>
+      All gradle builds use the same local repository as the Maven
+      builds and are told to always refresh the dependency cache.
+      This can be overriden on a per build basis, see below.  The
+      local repository is wiped out after each Gump run.
+    </p>
+<p>
+      All gradle builds are run using a special init script that adds
+      all snapshot repositories known to Gump as well as the local
+      maven repository as repositories and changes the version of all
+      dependencies to <span class="codefrag">integration.latest</span>.  This
means the
+      build will most likely use the latest SNAPSHOT build published
+      by the dependency - in general this is not the version just
+      built by Gump.
+    </p>
+<p>
+      Technically it is not necessary to declare the dependencies of a
+      gradle built project since artifacts will be retrieved even if
+      Gump doesn't know about the dependency.  Still it is better to
+      list all dependencies inside the Gump descriptor in order to
+      maintain correct build order.
+    </p>
 <table class="ForrestTable" cellspacing="1" cellpadding="4">
       
 <tr>
@@ -933,19 +898,32 @@ document.write("Last Published: " + docu
       
 <tr>
         
-<td colspan="1" rowspan="1">makefile</td>
-        <td colspan="1" rowspan="1">The make file to execute.  Defaults to <strong>Makefile</strong>.
-        </td>
-        <td colspan="1" rowspan="1">No Defaults to <strong>Makefile</strong>.</td>
+<td colspan="1" rowspan="1">task</td>
+        <td colspan="1" rowspan="1">The Gradle task to invoke.  <em>This can
be a comma
+        separated list. Spaces are preserved.</em></td>
+        <td colspan="1" rowspan="1">No. Defaults to <strong>build</strong>.</td>
       
 </tr>
       
 <tr>
         
-<td colspan="1" rowspan="1">target</td>
-        <td colspan="1" rowspan="1">The make target to invoke. <em>This can be
a comma
-        separated list. Spaces are preserved.</em></td>
-        <td colspan="1" rowspan="1">No. Defaults to <strong>ALL</strong>.</td>
+<td colspan="1" rowspan="1">separateLocalRepository</td>
+        <td colspan="1" rowspan="1">Normally all &lt;mvn&gt; and &lt;gradle&gt;
builds share the same local
+          repository that will be removed after each complete Gump run.
+          Sometimes a project needs to use a separate local repository
+          from the others, the most common case is that a project needs
+          to be built against a released dependency instead of a Gump
+          built one in order to break a dependency cycle.<br>
+          The value of this attribute can be a boolean or an
+          identifier.  If you use a boolean it simply en- or
+          disables a local repository separate from the other
+          directories and Gump will choose a directory name (if the
+          value is true).  If several projects are tightly related
+          and should share the same local repository different from
+          the other projects you can use an id instead of a boolean
+          and use the same id for each project.
+        </td>
+        <td colspan="1" rowspan="1">No. Defaults to <strong>false</strong>.</td>
       
 </tr>
     
@@ -953,10 +931,23 @@ document.write("Last Published: " + docu
 </div>
 
   
-<a name="nant"></a>
-<h2 class="boxed">nant</h2>
+<a name="script"></a>
+<h2 class="boxed">script</h2>
 <div class="section">
-<p>Specifies the arguments to be passed to <a target="_blank" href="http://nant.sourceforge.org/">NAnt</a>.</p>
+<p>Specifies a script to be executed in order to make build a
+    project.</p>
+<p>The assumption is that the script can be invoked in a platform
+    independent manner, though the contents of the script may be
+    platform specific.  Specifically, if the name of the script is
+    "name" and no file with the name "name" exists in the project's
+    basedir, it will be invoked as follows:</p>
+<ul>
+      
+<li>On Windows/batch, "call .\name.bat"</li>
+      
+<li>On Unix/bash, "./name.sh"</li>
+    
+</ul>
 <table class="ForrestTable" cellspacing="1" cellpadding="4">
       
 <tr>
@@ -969,33 +960,45 @@ document.write("Last Published: " + docu
       
 <tr>
         
-<td colspan="1" rowspan="1">buildfile</td>
-        <td colspan="1" rowspan="1">The NAnt build file to execute.  Defaults to
-        <strong>NAnt.build</strong>.
-        </td>
-        <td colspan="1" rowspan="1">No Defaults to <strong>NAnt.build</strong>.</td>
-      
-</tr>
-      
-<tr>
-        
-<td colspan="1" rowspan="1">target</td>
-        <td colspan="1" rowspan="1">The NAnt target to invoke. <em>This can be
a comma
-        separated list. Spaces are preserved.</em></td>
-        <td colspan="1" rowspan="1">No. Defaults to the default target defined by the
build file.</td>
+<td colspan="1" rowspan="1">name</td>
+        <td colspan="1" rowspan="1">The name of the script to execute.</td>
+        <td colspan="1" rowspan="1">Yes</td>
       
 </tr>
     
 </table>
+<p>Additional command line arguments can be specified using nested
+    &lt;arg&gt; elements.  If the name of an arg start with "--" or
+    doesn't start with "-", then a single argument gets created from
+    one &lt;arg&gt; element, using "=" to join name and value.  If it
+    starts with a single "-", two arguments get created, one for the
+    name and one for the value.  For example:</p>
+<pre class="code">
+      &lt;script name="foo"&gt;
+        &lt;arg name="--double-dash" value="1"/&gt;
+        &lt;arg name="-single-dash" value="2"/&gt;
+        &lt;arg name="no-dash" value="3"/&gt;
+      &lt;/script&gt;
+    </pre>
+<p>becomes</p>
+<pre class="code">
+      ./foo --double-dash=1 -single-dash 2 no-dash=3
+    </pre>
 </div>
 
   
-<a name="msbuild"></a>
-<h2 class="boxed">msbuild</h2>
+<a name="configure"></a>
+<h2 class="boxed">configure</h2>
 <div class="section">
-<p>Specifies the arguments to be passed to MSBuild or xbuild.
-    Gump will automatically detect whether MSBuild or xbuild is
-    present and run the appropriate tool - preferring MSBuild.</p>
+<p>Is a specialized version of <a href="#script">script</a>
+    with the fixed script name of "configure".</p>
+</div>
+
+  
+<a name="make"></a>
+<h2 class="boxed">make</h2>
+<div class="section">
+<p>Specifies the arguments to be passed to make.</p>
 <table class="ForrestTable" cellspacing="1" cellpadding="4">
       
 <tr>
@@ -1008,19 +1011,19 @@ document.write("Last Published: " + docu
       
 <tr>
         
-<td colspan="1" rowspan="1">buildfile</td>
-        <td colspan="1" rowspan="1">The MSBuild build file/project/solution to execute.
+<td colspan="1" rowspan="1">makefile</td>
+        <td colspan="1" rowspan="1">The make file to execute.  Defaults to <strong>Makefile</strong>.
         </td>
-        <td colspan="1" rowspan="1">No</td>
+        <td colspan="1" rowspan="1">No Defaults to <strong>Makefile</strong>.</td>
       
 </tr>
       
 <tr>
         
 <td colspan="1" rowspan="1">target</td>
-        <td colspan="1" rowspan="1">The MSBuild target to invoke. <em>This can
be a comma
+        <td colspan="1" rowspan="1">The make target to invoke. <em>This can be
a comma
         separated list. Spaces are preserved.</em></td>
-        <td colspan="1" rowspan="1">No. Defaults to the default target defined by the
build file.</td>
+        <td colspan="1" rowspan="1">No. Defaults to <strong>ALL</strong>.</td>
       
 </tr>
     
@@ -1028,39 +1031,10 @@ document.write("Last Published: " + docu
 </div>
 
   
-<a name="gradle"></a>
-<h2 class="boxed">gradle</h2>
+<a name="nant"></a>
+<h2 class="boxed">nant</h2>
 <div class="section">
-<p>
-<strong>The Gradle builder is a work in progress and may not be
-    working correctly.</strong>
-</p>
-<p>The <a target="_blank" href="http://gradle.org/">Gradle</a>
-    component of Gump (&lt;gradle&gt;) uses a
-    <strong>pre-installed</strong> version of <a target="_blank" href="http://gradle.org">Gradle</a>,
it does
-    <strong>NOT</strong> bootstrap Gradle itself.</p>
-<p>
-      All gradle builds use the same local repository as the Maven
-      builds and are told to always refresh the dependency cache.
-      This can be overriden on a per build basis, see below.  The
-      local repository is wiped out after each Gump run.
-    </p>
-<p>
-      All gradle builds are run using a special init script that adds
-      all snapshot repositories known to Gump as well as the local
-      maven repository as repositories and changes the version of all
-      dependencies to <span class="codefrag">integration.latest</span>.  This
means the
-      build will most likely use the latest SNAPSHOT build published
-      by the dependency - in general this is not the version just
-      built by Gump.
-    </p>
-<p>
-      Technically it is not necessary to declare the dependencies of a
-      gradle built project since artifacts will be retrieved even if
-      Gump doesn't know about the dependency.  Still it is better to
-      list all dependencies inside the Gump descriptor in order to
-      maintain correct build order.
-    </p>
+<p>Specifies the arguments to be passed to <a target="_blank" href="http://nant.sourceforge.org/">NAnt</a>.</p>
 <table class="ForrestTable" cellspacing="1" cellpadding="4">
       
 <tr>
@@ -1073,32 +1047,20 @@ document.write("Last Published: " + docu
       
 <tr>
         
-<td colspan="1" rowspan="1">task</td>
-        <td colspan="1" rowspan="1">The Gradle task to invoke.  <em>This can
be a comma
-        separated list. Spaces are preserved.</em></td>
-        <td colspan="1" rowspan="1">No. Defaults to <strong>build</strong>.</td>
+<td colspan="1" rowspan="1">buildfile</td>
+        <td colspan="1" rowspan="1">The NAnt build file to execute.  Defaults to
+        <strong>NAnt.build</strong>.
+        </td>
+        <td colspan="1" rowspan="1">No Defaults to <strong>NAnt.build</strong>.</td>
       
 </tr>
       
 <tr>
         
-<td colspan="1" rowspan="1">separateLocalRepository</td>
-        <td colspan="1" rowspan="1">Normally all &lt;mvn&gt; and &lt;gradle&gt;
builds share the same local
-          repository that will be removed after each complete Gump run.
-          Sometimes a project needs to use a separate local repository
-          from the others, the most common case is that a project needs
-          to be built against a released dependency instead of a Gump
-          built one in order to break a dependency cycle.<br>
-          The value of this attribute can be a boolean or an
-          identifier.  If you use a boolean it simply en- or
-          disables a local repository separate from the other
-          directories and Gump will choose a directory name (if the
-          value is true).  If several projects are tightly related
-          and should share the same local repository different from
-          the other projects you can use an id instead of a boolean
-          and use the same id for each project.
-        </td>
-        <td colspan="1" rowspan="1">No. Defaults to <strong>false</strong>.</td>
+<td colspan="1" rowspan="1">target</td>
+        <td colspan="1" rowspan="1">The NAnt target to invoke. <em>This can be
a comma
+        separated list. Spaces are preserved.</em></td>
+        <td colspan="1" rowspan="1">No. Defaults to the default target defined by the
build file.</td>
       
 </tr>
     
@@ -1144,6 +1106,44 @@ document.write("Last Published: " + docu
       
 </tr>
     
+</table>
+</div>
+
+  
+<a name="msbuild"></a>
+<h2 class="boxed">msbuild</h2>
+<div class="section">
+<p>Specifies the arguments to be passed to MSBuild or xbuild.
+    Gump will automatically detect whether MSBuild or xbuild is
+    present and run the appropriate tool - preferring MSBuild.</p>
+<table class="ForrestTable" cellspacing="1" cellpadding="4">
+      
+<tr>
+        
+<th colspan="1" rowspan="1">Attribute</th>
+        <th colspan="1" rowspan="1">Description</th>
+        <th colspan="1" rowspan="1">Required?</th>
+      
+</tr>
+      
+<tr>
+        
+<td colspan="1" rowspan="1">buildfile</td>
+        <td colspan="1" rowspan="1">The MSBuild build file/project/solution to execute.
+        </td>
+        <td colspan="1" rowspan="1">No</td>
+      
+</tr>
+      
+<tr>
+        
+<td colspan="1" rowspan="1">target</td>
+        <td colspan="1" rowspan="1">The MSBuild target to invoke. <em>This can
be a comma
+        separated list. Spaces are preserved.</em></td>
+        <td colspan="1" rowspan="1">No. Defaults to the default target defined by the
build file.</td>
+      
+</tr>
+    
 </table>
 </div>
 



Mime
View raw message