Author: buildbot
Date: Tue May 9 23:24:41 2017
New Revision: 1011977
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 Tue May 9 23:24:41 2017
@@ -108,7 +108,10 @@
</div></div><h3 id="Building-DoingaQuickBuild">Doing a Quick
Build</h3><p><strong>Available as of Camel 2.6</strong></p><p>The following
skips building the manual, the distro and does not execute the unit
tests.</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 install -Pfastinstall
]]></script>
-</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">
+</div></div><h3 id="Building-Updatingthelicenseheaders">Updating the license
headers</h3><p>Proper license headers are enforced using Apache RAT and
Checkstyle Maven plugins. To make it less tedious and error prone you can
update the license headers by using:</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 -Plicense license:format
+]]></script>
+</div></div><p>This can be invoked from any module, which makes it useful when
working on components. You can find the various license headers that the Camel
project uses in buildtools/src/main/resources/header-*.txt files. These are
regenerated at build time from header.txt in the same directory.</p><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-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">
Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
