Author: buildbot
Date: Mon Apr 8 20:23:18 2013
New Revision: 857781
Log:
Production update by buildbot for camel
Modified:
websites/production/camel/content/building.html
Modified: websites/production/camel/content/building.html
==============================================================================
--- websites/production/camel/content/building.html (original)
+++ websites/production/camel/content/building.html Mon Apr 8 20:23:18 2013
@@ -99,9 +99,16 @@
<p>To build camel maven has to be configured to use more memory</p>
+<h5><a shape="rect" name="Building-Unix%2FLinux%2FMac"></a>Unix/Linux/Mac</h5>
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
<pre class="code-java">
-set MAVEN_OPTS=<span class="code-quote">"-Xmx1024m -XX:MaxPermSize=512m"</span>
+export MAVEN_OPTS=<span class="code-quote">"-Xmx1024m
-XX:MaxPermSize=512m"</span>
+</pre>
+</div></div>
+<h5><a shape="rect" name="Building-Windows"></a>Windows</h5>
+<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
+<pre class="code-java">
+set MAVEN_OPTS=-Xmx1024m -XX:MaxPermSize=512m
</pre>
</div></div>
@@ -143,37 +150,55 @@ mvn install -Pfastinstall
<p>If you prefer to use an IDE then you can auto-generate the IDE's project
files using maven plugins. e.g.</p>
+<h4><a shape="rect" name="Building-IntelliJ"></a>IntelliJ</h4>
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
<pre class="code-java">
-mvn eclipse:eclipse
+mvn idea:idea
</pre>
</div></div>
-<p>or</p>
+<h4><a shape="rect" name="Building-Eclipse"></a>Eclipse</h4>
+<p>There are several ways to import the projects into Eclipse.</p>
+<h5><a shape="rect" name="Building-m2e"></a>m2e</h5>
+<p>At this point, usage of the m2e plugins to import Camel into Eclipse is
untested and unsupported. Patches, notes, etc... to help get this supported
would be more than welcome.</p>
+<h5><a shape="rect"
name="Building-maveneclipseplugin"></a>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" style="border-width: 1px;"><div class="codeContent
panelContent">
<pre class="code-java">
-mvn idea:idea
+mvn process-test-sources eclipse:eclipse
</pre>
</div></div>
-
-<h4><a shape="rect"
name="Building-AddingCamelEclipsetemplatestoyourworkspace"></a>Adding Camel
Eclipse templates to your workspace</h4>
-
+<p>or</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
<pre class="code-java">
mvn -Psetup.eclipse -Declipse.workspace.dir=/path/to/your/workspace
</pre>
</div></div>
-<p>You can also find some helpful notes on usage <a shape="rect"
class="external-link"
href="http://janstey.blogspot.com/2008/08/eclipse-templates-for-apache-camel.html";
rel="nofollow">here</a>. </p>
+<p>The latter is recommended as it would completely setup the workspace for
you as well as provide options to wire in other projects also found in your
workspace.</p>
+
+<p>After running the above command, from within Eclipse, do "File -> Import
-> Existing Projects into Workspace", select the root camel checkout
location and Eclipse should find all the projects. </p>
+
+<h5><a shape="rect"
name="Building-AddingCamelEclipsetemplatestoyourworkspace"></a>Adding Camel
Eclipse templates to your workspace</h5>
-<h4><a shape="rect" name="Building-ImportingintoEclipse"></a>Importing into
Eclipse</h4>
-<p>If you have not already done so, you will need to make Eclipse aware of the
Maven repository so that it can build everything. In the preferences, go to
Java->Build Path->Classpath and define a new Classpath Variable named
M2_REPO that points to your local Maven repository (i.e.,
<tt>~/.m2/repository</tt> on Unix and <tt>c:\Documents and
Settings\<user>\.m2\repository</tt> on Windows).</p>
+<p>The above mentioned setup.eclipse profile does a few additional things to
your workspace:</p>
-<p>You can also get Maven to do this for you:</p>
+<ol><li>Adds the Camel code templates (see <a shape="rect"
class="external-link"
href="http://janstey.blogspot.com/2008/08/eclipse-templates-for-apache-camel.html";
rel="nofollow">here</a>)</li><li>Sets the M2_REPO variable in the workspace
that points to your local Maven repository (i.e., <tt>~/.m2/repository</tt> on
Unix and <tt>c:\Documents and Settings\<user>\.m2\repository</tt> on
Windows) which allows the jars to be resolved.</li></ol>
+
+
+<h5><a shape="rect"
name="Building-Hint%3Aspecifytheworkspacelocationinyour.m2%2Fsettings.xml"></a>Hint:
specify the workspace location in your .m2/settings.xml</h5>
+<p>You can add a profile to your .m2/settings.xml to specify your eclipse
workspace location so you can avoid having to type that each time you need to
update the projects.</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
-<pre class="code-java">
-mvn eclipse:configure-workspace -Declipse.workspace=/path/to/the/workspace/
+<pre class="code-xml">
+<span class="code-tag"><profiles></span>
+ <span class="code-tag"><profile></span>
+ <span class="code-tag"><id></span>setup.eclipse<span
class="code-tag"></id></span>
+ <span class="code-tag"><properties></span>
+ <span
class="code-tag"><eclipse.workspace></span>/path/to/your/workspace<span
class="code-tag"></eclipse.workspace></span>
+ <span class="code-tag"></properties></span>
+ <span class="code-tag"></profile></span>
+<span class="code-tag"></profiles></span>
</pre>
</div></div>
