svn commit: r898918 - in /websites/production/camel/content: building.html cache/main.pageCache

[bu...@apache.org]

Author: buildbot
Date: Sun Feb 23 08:18:51 2014
New Revision: 898918

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 Sun Feb 23 08:18:51 2014
@@ -110,17 +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>At this point, usage of the m2e plugins to import Camel into Eclipse does not work due to plugins without LifeCycle hints, bundle plugin configuration problems, etc... Patches, notes, etc... to help get this supported would be more than welcome.</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="theme: Default; brush: text; gutter: false" type="syntaxhighlighter"><![CDATA[mvn process-test-sources eclipse:eclipse
 ]]></script>
-</div></div>    <div class="aui-message success shadowed information-macro">
-                    <p class="title">Enable the apt Profile explicitly if using Java 6</p>
-                            <span class="aui-icon icon-success">Icon</span>
-                <div class="message-content">
-                            <p>Per default this profile is enabled <strong>only</strong> when using Java 7+ however for many of the Camel components you would still need the <code>org.apache.camel:spi-annotations</code> Maven module on the class path inside the generated <code>.classpath</code>. To force this on Java 6 do:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: text; gutter: false" type="syntaxhighlighter"><![CDATA[mvn -Papt process-test-sources eclipse:eclipse
-]]></script>
-</div></div><p>As otherwise some of the Camel components inside your eclipse workspace would not compile (when using Java 6) because the <code>org.apache.camel:spi-annotations</code> Maven module would be missing on the class path.</p>
-                    </div>
-    </div>
-<p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</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">
 <script class="theme: Default; brush: text; gutter: false" type="syntaxhighlighter"><![CDATA[mvn -Psetup.eclipse -Declipse.workspace.dir=/path/to/your/workspace
 ]]></script>
 </div></div><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 -&gt; Import -&gt; Existing Projects into Workspace", select the root camel checkout location and Eclipse should find all the projects.</p><h5 id="Building-AddingCamelEclipsetemplatestoyourworkspace">Adding Camel Eclipse templates to your workspace</h5><p>The above mentioned setup.eclipse profile does a few additional things to your workspace:</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., <code>~/.m2/repository</code> on Unix and <code>c:\Documents and Settings\&lt;user&gt;\.m2\repository</code> on Wi
 ndows) which allows the jars to be resolved.</li></ol><h5 id="Building-Hint:specifytheworkspacelocationinyour.m2/settings.xml">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 pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">

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