camel-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r983661 - in /websites/production/camel/content: building.html cache/main.pageCache
Date Fri, 25 Mar 2016 06:19:33 GMT
Author: buildbot
Date: Fri Mar 25 06:19:32 2016
New Revision: 983661

Log:
Production update by buildbot for camel

Modified:
    websites/production/camel/content/building.html
    websites/production/camel/content/cache/main.pageCache

Modified: websites/production/camel/content/building.html
==============================================================================
--- websites/production/camel/content/building.html (original)
+++ websites/production/camel/content/building.html Fri Mar 25 06:19:32 2016
@@ -86,7 +86,7 @@
 	<tbody>
         <tr>
         <td valign="top" width="100%">
-<div class="wiki-content maincontent"><h2 id="Building-BuildingCamelfromSource">Building
Camel from Source</h2><p>Camel uses <a shape="rect" class="external-link" href="http://maven.apache.org/">Maven</a>
as its build and management tool. If you don't fancy using Maven you can use your IDE directly
or <a shape="rect" href="download.html">Download</a> a distribution or JAR.</p><h3
id="Building-Prequisites">Prequisites</h3><p><strong>Required:</strong></p><ul><li>Download
and <a shape="rect" class="external-link" href="http://maven.apache.org/download.html">install
Maven</a><br clear="none"> (Maven 3.1.1 or newer is required to build Camel 2.14
onwards)</li><li>Get the latest <a shape="rect" href="source.html">Source</a></li><li>Java<br
clear="none">(1.7 or 1.8 to build Camel 2.14 onwards)</li></ul><p><strong>Optional:</strong></p><ul><li><a
shape="rect" class="external-link" href="http://www.princexml.com/download/" rel="nofollow">Prince</a>
should be in the executable PATH to genera
 te the PDF documentation</li></ul><h3 id="Building-Mavenoptions">Maven
options</h3><p>To build camel maven has to be configured to use more memory</p><h5
id="Building-Unix/Linux/Mac">Unix/Linux/Mac</h5><div class="code panel pdl" style="border-width:
1px;"><div class="codeContent panelContent pdl">
+<div class="wiki-content maincontent"><h2 id="Building-BuildingCamelfromSource">Building
Camel from Source</h2><p>Camel uses <a shape="rect" class="external-link" href="http://maven.apache.org/">Maven</a>
as its build and management tool. If you don't fancy using Maven you can use your IDE directly
or <a shape="rect" href="download.html">Download</a> a distribution or JAR.</p><h3
id="Building-Prequisites">Prequisites</h3><p><strong>Required:</strong></p><ul><li>Download
and <a shape="rect" class="external-link" href="http://maven.apache.org/download.html">install
Maven</a><br clear="none"> (Maven 3.1.1 or newer is required to build Camel 2.14
onwards)<br clear="none">(Maven 3.2.5 or newer is required to build Camel 2.18 onwards)&#160;</li><li>Get
the latest <a shape="rect" href="source.html">Source</a></li><li>Java<br
clear="none">(1.7 or 1.8 to build Camel 2.14 onwards)<br clear="none">(1.8 to build
Camel 2.18 onwards)&#160;</li></ul><p><strong>Optional:</strong></p><ul><li><a
shap
 e="rect" class="external-link" href="http://www.princexml.com/download/" rel="nofollow">Prince</a>
should be in the executable PATH to generate the PDF documentation</li></ul><h3
id="Building-Mavenoptions">Maven options</h3><p>To build camel maven has to
be configured to use more memory</p><h5 id="Building-Unix/Linux/Mac">Unix/Linux/Mac</h5><div
class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent
pdl">
 <script class="brush: text; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[export
MAVEN_OPTS=&quot;-Xms2048m -Xmx2048m -XX:MaxPermSize=512m&quot;
 ]]></script>
 </div></div><h5 id="Building-Windows">Windows</h5><div class="code
panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
@@ -110,7 +110,7 @@
 </div></div><h4 id="Building-Eclipse">Eclipse</h4><p>There
are several ways to import the projects into Eclipse.</p><h5 id="Building-m2e">m2e</h5><p>Starting
with Camel 2.14.0, Camel can be imported into Eclipse using m2e Maven integration.</p><p>Before
you start: It is important to run Eclipse with at least 1.5 GB of heap memory, otherwise the
import process will fail. To increase the heap size, edit the "eclipse.ini" file and set the
-Xmx parameter as follows:</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>eclipse.ini</b></div><div
class="codeContent panelContent pdl">
 <script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[[...]
 -Xmx1536m]]></script>
-</div></div><h6 id="Building-CloningtheGitRepository">Cloning the Git Repository&#160;</h6><p>Either
follow instructions about getting the latest <a shape="rect" href="source.html">source</a>,
or clone the Git repository with Eclipse by selecting "File -&gt; Import -&gt; Git
/ Projects from Git" and "Clone URI". Provide all repository details in the import wizard
and clone the repository into a directory outside of the Eclipse workspace. Once cloning has
completed, exit the import project wizard (i.e. simply select cancel when asked to select
"Wizard for project import").</p><h6 id="Building-ImportMavenProjects">Import
Maven Projects</h6><p>Import Camel projects as Maven projects using m2e by selecting
"File -&gt; Import -&gt; Maven -&gt; Existing Maven Projects". Point the wizard
to the root directory of the cloned repository. Eclipse will analyze all Camel projects and
eventually present the following summary:</p><p><span class="confluence-embedded-file-wrapper
confluence-embedded
 -manual-size"><img class="confluence-embedded-image confluence-thumbnail" width="300"
src="building.thumbs/camel-eclipse-m2e-import.png" data-image-src="/confluence/download/attachments/49126/camel-eclipse-m2e-import.png?version=1&amp;modificationDate=1396491620000&amp;api=v2"
data-unresolved-comment-count="0" data-linked-resource-id="40894772" data-linked-resource-version="1"
data-linked-resource-type="attachment" data-linked-resource-default-alias="camel-eclipse-m2e-import.png"
data-base-url="https://cwiki.apache.org/confluence" data-linked-resource-content-type="image/png"
data-linked-resource-container-id="49126" data-linked-resource-container-version="76"></span></p><p>Simply
confirm the import of all projects by clicking "Finish". The import process will create Eclipse
projects and automatically set up build paths using dependency details provided by the pom.xml
files. Once completed, all Camel projects will be available in your workspace:</p><p><span
class="confluence-embedde
 d-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image
confluence-thumbnail" width="300" src="building.thumbs/camel-eclipse-m2e-import-completed.png"
data-image-src="/confluence/download/attachments/49126/camel-eclipse-m2e-import-completed.png?version=1&amp;modificationDate=1396491969000&amp;api=v2"
data-unresolved-comment-count="0" data-linked-resource-id="40894773" data-linked-resource-version="1"
data-linked-resource-type="attachment" data-linked-resource-default-alias="camel-eclipse-m2e-import-completed.png"
data-base-url="https://cwiki.apache.org/confluence" data-linked-resource-content-type="image/png"
data-linked-resource-container-id="49126" data-linked-resource-container-version="76"></span></p><h5
id="Building-maven-eclipse-plugin">maven-eclipse-plugin</h5><p>The maven-eclipse-plugin
can be used to generate the .classpath/.project/.settings file that Eclipse need. To do this,
run:</p><div class="code panel pdl" style="border-width: 1px;"><div
  class="codeContent panelContent pdl">
+</div></div><h6 id="Building-CloningtheGitRepository">Cloning the Git Repository&#160;</h6><p>Either
follow instructions about getting the latest <a shape="rect" href="source.html">source</a>,
or clone the Git repository with Eclipse by selecting "File -&gt; Import -&gt; Git
/ Projects from Git" and "Clone URI". Provide all repository details in the import wizard
and clone the repository into a directory outside of the Eclipse workspace. Once cloning has
completed, exit the import project wizard (i.e. simply select cancel when asked to select
"Wizard for project import").</p><h6 id="Building-ImportMavenProjects">Import
Maven Projects</h6><p>Import Camel projects as Maven projects using m2e by selecting
"File -&gt; Import -&gt; Maven -&gt; Existing Maven Projects". Point the wizard
to the root directory of the cloned repository. Eclipse will analyze all Camel projects and
eventually present the following summary:</p><p><span class="confluence-embedded-file-wrapper
confluence-embedded
 -manual-size"><img class="confluence-embedded-image confluence-thumbnail" width="300"
src="building.thumbs/camel-eclipse-m2e-import.png" data-image-src="/confluence/download/attachments/49126/camel-eclipse-m2e-import.png?version=1&amp;modificationDate=1396491620000&amp;api=v2"
data-unresolved-comment-count="0" data-linked-resource-id="40894772" data-linked-resource-version="1"
data-linked-resource-type="attachment" data-linked-resource-default-alias="camel-eclipse-m2e-import.png"
data-base-url="https://cwiki.apache.org/confluence" data-linked-resource-content-type="image/png"
data-linked-resource-container-id="49126" data-linked-resource-container-version="77"></span></p><p>Simply
confirm the import of all projects by clicking "Finish". The import process will create Eclipse
projects and automatically set up build paths using dependency details provided by the pom.xml
files. Once completed, all Camel projects will be available in your workspace:</p><p><span
class="confluence-embedde
 d-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image
confluence-thumbnail" width="300" src="building.thumbs/camel-eclipse-m2e-import-completed.png"
data-image-src="/confluence/download/attachments/49126/camel-eclipse-m2e-import-completed.png?version=1&amp;modificationDate=1396491969000&amp;api=v2"
data-unresolved-comment-count="0" data-linked-resource-id="40894773" data-linked-resource-version="1"
data-linked-resource-type="attachment" data-linked-resource-default-alias="camel-eclipse-m2e-import-completed.png"
data-base-url="https://cwiki.apache.org/confluence" data-linked-resource-content-type="image/png"
data-linked-resource-container-id="49126" data-linked-resource-container-version="77"></span></p><h5
id="Building-maven-eclipse-plugin">maven-eclipse-plugin</h5><p>The maven-eclipse-plugin
can be used to generate the .classpath/.project/.settings file that Eclipse need. To do this,
run:</p><div class="code panel pdl" style="border-width: 1px;"><div
  class="codeContent panelContent pdl">
 <script class="brush: text; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[mvn
process-test-sources eclipse:eclipse
 ]]></script>
 </div></div><p><span style="line-height: 1.4285715;">or</span></p><div
class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent
pdl">
@@ -132,19 +132,7 @@
 </div></div><h3 id="Building-Buildingsourcejars">Building source jars</h3><p>If
you want to build jar files with the source code, that for instance Eclipse can important
so you can debug the Camel code as well. Then you can run this command from the camel root
folder:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
 <script class="brush: text; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[mvn
clean source:jar install -Pfastinstall
 ]]></script>
-</div></div><h3 id="Building-BuildingwithSpring3.0">Building with Spring
3.0</h3><div class="confluence-information-macro confluence-information-macro-information"><span
class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>Support for Spring 3.0 is deprecated
from Camel 2.11 onwards.</p></div></div><p>From Camel 2.11.0 onwards,
if you want Camel to be build against Spring 3.0 you have to build with the maven profile
<code>spring3.0</code>.</p><div class="code panel pdl" style="border-width:
1px;"><div class="codeContent panelContent pdl">
-<script class="brush: text; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[mvn
clean install -Pspring3.0
-]]></script>
-</div></div><h3 id="Building-BuildingwithSpring3.1">Building with Spring
3.1</h3><p>From Camel 2.10.0 onwards, if you want Camel to be build against Spring
3.1 you have to build with the maven profile <code>spring3.1</code>.</p><div
class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent
pdl">
-<script class="brush: text; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[mvn
clean install -Pspring3.1
-]]></script>
-</div></div><p>From Camel 2.11.0 onwards, Spring 3.1 is the default.</p><p><strong>Note:</strong>
the <code>camel-test-spring</code> component requires to be built with Spring
3.1.</p><h3 id="Building-BuildingwithSpring3.2">Building with Spring 3.2</h3><p>From
Camel 2.11.0 onwards, if you want Camel to be build against Spring 3.2 you have to build with
the maven profile <code>spring3.2</code>.</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: text; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[mvn
clean install -Pspring3.2
-]]></script>
-</div></div><p>From Camel 2.12.0 onwards, Spring 3.2 is the default.</p><p>&#160;</p><h3
id="Building-BuildingwithSpring4.0">Building with Spring 4.0</h3><p>From Camel
2.13.0 onwards, if you want Camel to be build against Spring 4.0 to work around the back compatible
issue&#160;<a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/CAMEL-7074"
style="line-height: 1.4285715;">CAMEL-7074</a><span style="line-height: 1.4285715;">,
you have to build with the maven profile&#160;</span><code style="line-height:
1.4285715;">spring4</code><span style="line-height: 1.4285715;">.</span></p><div
class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent
pdl">
-<script class="brush: text; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[mvn
clean install -Pspring4
-]]></script>
-</div></div><p>From Camel 2.12.0 onwards, Spring 3.2 is the default.</p><h3
id="Building-Workingwithfeatures">Working with features</h3><p>If you change
anything in the features.xml from <code>platform/karaf</code> you can run a validation
step to ensure the generated features.xml file is correct. You can do this running the following
maven goal from the <code>platform</code> directory.</p><div class="code
panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><h3 id="Building-Workingwithkaraffeatures">Working with karaf
features</h3><p>If you change anything in the features.xml from <code>platform/karaf</code>
you can run a validation step to ensure the generated features.xml file is correct. You can
do this running the following maven goal from the <code>platform</code> directory.</p><div
class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent
pdl">
 <script class="brush: text; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[mvn
clean install -Pvalidate
 ]]></script>
 </div></div><h3 id="Building-ExecutingunittestsusingEkstazi">Executing
unit tests using Ekstazi</h3><p>Normally, when you execute the unit tests during
your development cycle for a particular component, you are executing all the tests each time.
This may become inefficient, when you are changing one class and the effect of this change
is limited within the component having many unit tests. Ekstazi is a regression testing tool
that can keep track of the test results and the changed classes so that unaffected tests can
be skipped during the subsequent testing. For more details of Ekstazi, please refer to the
Ekstazi page at&#160;<a shape="rect" class="external-link" href="http://www.ekstazi.org"
rel="nofollow">http://www.ekstazi.org</a>.</p><p><span style="line-height:
1.4285715;">To use Ekstazi, you can run the tests with the maven profile ekstazi.</span></p><div
class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent
pdl">

Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.



Mime
View raw message