servicemix-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ge...@apache.org
Subject svn commit: r1597941 [5/6] - in /servicemix/site/production/docs/5.0.x: ./ activemq/ activiti/ camel/ camel/deployment/ commands/ developers-guide/ karaf/ quickstart/ user/ users-guide/
Date Wed, 28 May 2014 08:20:18 GMT
Modified: servicemix/site/production/docs/5.0.x/developers-guide/features-maven-plugin-generate.html
URL: http://svn.apache.org/viewvc/servicemix/site/production/docs/5.0.x/developers-guide/features-maven-plugin-generate.html?rev=1597941&r1=1597940&r2=1597941&view=diff
==============================================================================
--- servicemix/site/production/docs/5.0.x/developers-guide/features-maven-plugin-generate.html (original)
+++ servicemix/site/production/docs/5.0.x/developers-guide/features-maven-plugin-generate.html Wed May 28 08:20:15 2014
@@ -94,44 +94,12 @@
 </ul>
         </div>
         <div id="body">
-                              <h2 id="Goalfeaturesgenerate">Goal <tt>features:generate</tt></h2><p>The <tt>features:generate</tt> goal generates a features XML file for every bundle listed in the project's dependencies.  In order to satisfy the required imports in these bundles, the plugin will add bundles:</p><ul style="list-style: square"><li><p>bundles provided by Apache Karaf</p></li><li><p>a explicit list of bundles</p></li><li><p>bundles discovered in the POM's transitive dependencies</p></li></ul><p>Afterwards, the generated file will be attached to the build as an additional build artifact (by default as <tt>group:artifact:version:xml:features</tt>).</p><h3 id="Example">Example</h3><p>The example below generates one feature that installs bundle <tt>mvn:org.apache:bundle1:1.0</tt> in a features XML file called <tt>target/features.xml</tt>.  It will find bundle in Apache Karaf 2.3.0, the transitive dependencies for this POM and the bundles listed in <tt>src/main/resources/bund
 les.properties</tt>. </p><div class="syntax"><pre name='code' class='brush: xml; gutter: false;'><code>
-&lt;project&gt;
-  &lt;dependencies&gt;
-    &lt;dependency&gt;
-      &lt;groupId&gt;org.apache&lt;/groupId&gt;
-      &lt;artifactId&gt;bundle1&lt;/artifactId&gt;
-      &lt;version&gt;1.0&lt;/version&gt;
-    &lt;/dependency&gt;
-  &lt;/dependencies&gt;
-  &lt;build&gt;
-    &lt;plugins&gt;
-      &lt;plugin&gt;
-        &lt;groupId&gt;org.apache.karaf.tooling&lt;/groupId&gt;
-        &lt;artifactId&gt;features-maven-plugin&lt;/artifactId&gt;
-        &lt;version&gt;2.3.0&lt;/version&gt;
-          &lt;executions&gt;
-            &lt;execution&gt;
-              &lt;id&gt;generate&lt;/id&gt;
-              &lt;phase&gt;generate-resources&lt;/phase&gt;
-              &lt;goals&gt;
-                &lt;goal&gt;generate&lt;/goal&gt;
-              &lt;/goals&gt;
-              &lt;configuration&gt;
-                &lt;bundles&gt;src/main/resources/bundles.properties&lt;/bundles&gt;
-                &lt;kernelVersion&gt;2.3.0&lt;/kernelVersion&gt;
-                &lt;outputFile&gt;target/features.xml&lt;/outputFile&gt;
-              &lt;/configuration&gt;
-            &lt;/execution&gt;
-          &lt;/executions&gt;
-        &lt;/plugin&gt;
-    &lt;/plugins&gt;
-  &lt;/build&gt;  
-&lt;/project&gt;</code></pre></div><h3 id="Parameters">Parameters</h3><div class="table-wrap"><table class="confluenceTable"><tr><th class="confluenceTh"> Name </th><th class="confluenceTh"> Type </th><th class="confluenceTh"> Description </th></tr><tr><td class="confluenceTd"> <tt>outputFile</tt> </td><td class="confluenceTd"> <tt>File</tt> </td><td class="confluenceTd"> Name of the features XML file that is being generated <br/> Default value: <tt>/x1/asf/karaf-2.3.x/target/checkout/manual/target/classes/feature.xml</tt> </td></tr><tr><td class="confluenceTd"> <tt>attachmentArtifactType</tt> </td><td class="confluenceTd"> <tt>String</tt> </td><td class="confluenceTd"> The artifact type for attaching the generated file to the project <br/> Default value: {{xml}) </td></tr><tr><td class="confluenceTd"> <tt>attachmentArtifactClassifier</tt> </td><td class="confluenceTd"> <tt>String</tt> </td><td class="confluenceTd"> The artifact classifier for attaching the generated file to the pro
 ject <br/> Default value: <tt>features</tt> </td></tr><tr><td class="confluenceTd"> <tt>kernelVersion</tt> </td><td class="confluenceTd"> <tt>String</tt> </td><td class="confluenceTd"> The version of Karaf that is used to determine system bundles and default provided features </td></tr><tr><td class="confluenceTd"> <tt>bundles</tt> </td><td class="confluenceTd"> <tt>File</tt> </td><td class="confluenceTd"> A properties file that contains a list of bundles that will be used to generate the features.xml file </td></tr></table></div>
+                              <h2 id="Goalfeaturesgenerate">Goal <tt>features:generate</tt></h2><p>The <tt>features:generate</tt> goal generates a features XML file for every bundle listed in the project's dependencies.  In order to satisfy the required imports in these bundles, the plugin will add bundles:</p><ul style="list-style: square"><li><p>bundles provided by Apache Karaf</p></li><li><p>a explicit list of bundles</p></li><li><p>bundles discovered in the POM's transitive dependencies</p></li></ul><p>Afterwards, the generated file will be attached to the build as an additional build artifact (by default as <tt>group:artifact:version:xml:features</tt>).</p><h3 id="Example">Example</h3><p>The example below generates one feature that installs bundle <tt>mvn:org.apache:bundle1:1.0</tt> in a features XML file called <tt>target/features.xml</tt>.  It will find bundle in Apache Karaf 2.3.0, the transitive dependencies for this POM and the bundles listed in <tt>src/main/resources/bund
 les.properties</tt>. </p><div class="syntax"><div class="highlight"><pre><span class="nt">&lt;project&gt;</span>&#x000A;  <span class="nt">&lt;dependencies&gt;</span>&#x000A;    <span class="nt">&lt;dependency&gt;</span>&#x000A;      <span class="nt">&lt;groupId&gt;</span>org.apache<span class="nt">&lt;/groupId&gt;</span>&#x000A;      <span class="nt">&lt;artifactId&gt;</span>bundle1<span class="nt">&lt;/artifactId&gt;</span>&#x000A;      <span class="nt">&lt;version&gt;</span>1.0<span class="nt">&lt;/version&gt;</span>&#x000A;    <span class="nt">&lt;/dependency&gt;</span>&#x000A;  <span class="nt">&lt;/dependencies&gt;</span>&#x000A;  <span class="nt">&lt;build&gt;</span>&#x000A;    <span class="nt">&lt;plugins&gt;</span>&#x000A;      <span class="nt">&lt;plugin&gt;</span>&#x000A;        <span class="nt">&lt;groupId&gt;</span>org.apache.karaf.tooling<span class="nt">&lt;/groupId&gt;</span>&#x000A;        <span class="nt">&lt;artifactId&gt;</span>features-maven-plugin<span class="n
 t">&lt;/artifactId&gt;</span>&#x000A;        <span class="nt">&lt;version&gt;</span>2.3.0<span class="nt">&lt;/version&gt;</span>&#x000A;          <span class="nt">&lt;executions&gt;</span>&#x000A;            <span class="nt">&lt;execution&gt;</span>&#x000A;              <span class="nt">&lt;id&gt;</span>generate<span class="nt">&lt;/id&gt;</span>&#x000A;              <span class="nt">&lt;phase&gt;</span>generate-resources<span class="nt">&lt;/phase&gt;</span>&#x000A;              <span class="nt">&lt;goals&gt;</span>&#x000A;                <span class="nt">&lt;goal&gt;</span>generate<span class="nt">&lt;/goal&gt;</span>&#x000A;              <span class="nt">&lt;/goals&gt;</span>&#x000A;              <span class="nt">&lt;configuration&gt;</span>&#x000A;                <span class="nt">&lt;bundles&gt;</span>src/main/resources/bundles.properties<span class="nt">&lt;/bundles&gt;</span>&#x000A;                <span class="nt">&lt;kernelVersion&gt;</span>2.3.0<span class="nt">&lt;/kernel
 Version&gt;</span>&#x000A;                <span class="nt">&lt;outputFile&gt;</span>target/features.xml<span class="nt">&lt;/outputFile&gt;</span>&#x000A;              <span class="nt">&lt;/configuration&gt;</span>&#x000A;            <span class="nt">&lt;/execution&gt;</span>&#x000A;          <span class="nt">&lt;/executions&gt;</span>&#x000A;        <span class="nt">&lt;/plugin&gt;</span>&#x000A;    <span class="nt">&lt;/plugins&gt;</span>&#x000A;  <span class="nt">&lt;/build&gt;</span>  &#x000A;<span class="nt">&lt;/project&gt;</span>&#x000A;</pre></div>&#x000A;</div><h3 id="Parameters">Parameters</h3><div class="table-wrap"><table class="confluenceTable"><tr><th class="confluenceTh"> Name </th><th class="confluenceTh"> Type </th><th class="confluenceTh"> Description </th></tr><tr><td class="confluenceTd"> <tt>outputFile</tt> </td><td class="confluenceTd"> <tt>File</tt> </td><td class="confluenceTd"> Name of the features XML file that is being generated <br/> Default value: <tt>/x
 1/asf/karaf-2.3.x/target/checkout/manual/target/classes/feature.xml</tt> </td></tr><tr><td class="confluenceTd"> <tt>attachmentArtifactType</tt> </td><td class="confluenceTd"> <tt>String</tt> </td><td class="confluenceTd"> The artifact type for attaching the generated file to the project <br/> Default value: {{xml}) </td></tr><tr><td class="confluenceTd"> <tt>attachmentArtifactClassifier</tt> </td><td class="confluenceTd"> <tt>String</tt> </td><td class="confluenceTd"> The artifact classifier for attaching the generated file to the project <br/> Default value: <tt>features</tt> </td></tr><tr><td class="confluenceTd"> <tt>kernelVersion</tt> </td><td class="confluenceTd"> <tt>String</tt> </td><td class="confluenceTd"> The version of Karaf that is used to determine system bundles and default provided features </td></tr><tr><td class="confluenceTd"> <tt>bundles</tt> </td><td class="confluenceTd"> <tt>File</tt> </td><td class="confluenceTd"> A properties file that contains a list of bund
 les that will be used to generate the features.xml file </td></tr></table></div>
         </div>
       
           </div>
     <div id="siteFooter">
-      &copy; 2008-2012 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
+      &copy; 2008-2014 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
       <br/>
       Apache ServiceMix, ServiceMix, Apache, the Apache feather logo, and the Apache ServiceMix project logo are trademarks of The Apache Software Foundation.
     </div>

Modified: servicemix/site/production/docs/5.0.x/developers-guide/features-maven-plugin-validate.html
URL: http://svn.apache.org/viewvc/servicemix/site/production/docs/5.0.x/developers-guide/features-maven-plugin-validate.html?rev=1597941&r1=1597940&r2=1597941&view=diff
==============================================================================
--- servicemix/site/production/docs/5.0.x/developers-guide/features-maven-plugin-validate.html (original)
+++ servicemix/site/production/docs/5.0.x/developers-guide/features-maven-plugin-validate.html Wed May 28 08:20:15 2014
@@ -94,43 +94,12 @@
 </ul>
         </div>
         <div id="body">
-                              <h2 id="Goalfeaturesvalidate">Goal <tt>features:validate</tt></h2><p>The <tt>features:validate</tt> goal validates a features XML descriptor by checking if all the required imports for the bundles defined in the features can be matched to a provided export.</p><p>By default, the plugin tries to add the Karaf standard features (standard and enterprise) in the repositories set.<br/>It means that it's not necessary to explicitly define the Karaf features descriptor in the repository section of your features descriptor.</p><h3 id="Example">Example</h3><p>The example below validates the features defined in the <tt>target/features.xml</tt> by checking all the imports and exports.  It reads the definition for the packages that are exported by the system bundle from the <tt>src/main/resources/config.properties</tt> file.</p><div class="syntax"><pre name='code' class='brush: xml; gutter: false;'><code>
-&lt;project&gt;
-  &lt;build&gt;
-    &lt;plugins&gt;
-      &lt;plugin&gt;
-        &lt;groupId&gt;org.apache.karaf.tooling&lt;/groupId&gt;
-        &lt;artifactId&gt;features-maven-plugin&lt;/artifactId&gt;
-        &lt;version&gt;2.3.0&lt;/version&gt;
-          &lt;executions&gt;
-            &lt;execution&gt;
-              &lt;id&gt;validate&lt;/id&gt;
-              &lt;phase&gt;process-resources&lt;/phase&gt;
-              &lt;goals&gt;
-                &lt;goal&gt;validate&lt;/goal&gt;
-              &lt;/goals&gt;
-              &lt;configuration&gt;
-                &lt;file&gt;target/features.xml&lt;/file&gt;
-                &lt;karafConfig&gt;src/main/resources/config.properties&lt;/karafConfig&gt;
-              &lt;/configuration&gt;
-            &lt;/execution&gt;
-          &lt;/executions&gt;
-          &lt;dependencies&gt;
-            &lt;dependency&gt;
-              &lt;groupId&gt;org.slf4j&lt;/groupId&gt;
-              &lt;artifactId&gt;slf4j-simple&lt;/artifactId&gt;
-              &lt;version&gt;1.4.3&lt;/version&gt;
-	        &lt;/dependency&gt;
-          &lt;/dependencies&gt;
-        &lt;/plugin&gt;
-    &lt;/plugins&gt;
-  &lt;/build&gt;  
-&lt;/project&gt;</code></pre></div><h3 id="Parameters">Parameters</h3><div class="table-wrap"><table class="confluenceTable"><tr><th class="confluenceTh"> Name </th><th class="confluenceTh"> Type </th><th class="confluenceTh"> Description </th></tr><tr><td class="confluenceTd"> <tt>file</tt> </td><td class="confluenceTd"> <tt>File</tt> </td><td class="confluenceTd"> The features XML descriptor file to validate. <br/> Default value: <tt>/x1/asf/karaf-2.3.x/target/checkout/manual/target/classes/features.xml</tt> </td></tr><tr><td class="confluenceTd"> <tt>karafConfig</tt> </td><td class="confluenceTd"> <tt>String</tt> </td><td class="confluenceTd"> The Karaf <tt>config.properties</tt> file to use during the validation process <br/> Default value: <tt>config.properties</tt> </td></tr><tr><td class="confluenceTd"> <tt>jreVersion</tt> </td><td class="confluenceTd"> <tt>String</tt> </td><td class="confluenceTd"> The JRE version that is used during the validation process <br/> Default valu
 e: {{jre-1.5}) </td></tr><tr><td class="confluenceTd"> <tt>karafVersion</tt> </td><td class="confluenceTd"> <tt>String</tt> </td><td class="confluenceTd"> The target Karaf version used to get the Karaf core features (standard and enterprise) <br/> Default value is the version of the plugin </td></tr><tr><td class="confluenceTd"> <tt>repositories</tt> </td><td class="confluenceTd"> <tt>String[]</tt> </td><td class="confluenceTd"> Additional features XML descriptors that will be used during the validation process </td></tr></table></div>
+                              <h2 id="Goalfeaturesvalidate">Goal <tt>features:validate</tt></h2><p>The <tt>features:validate</tt> goal validates a features XML descriptor by checking if all the required imports for the bundles defined in the features can be matched to a provided export.</p><p>By default, the plugin tries to add the Karaf standard features (standard and enterprise) in the repositories set.<br/>It means that it's not necessary to explicitly define the Karaf features descriptor in the repository section of your features descriptor.</p><h3 id="Example">Example</h3><p>The example below validates the features defined in the <tt>target/features.xml</tt> by checking all the imports and exports.  It reads the definition for the packages that are exported by the system bundle from the <tt>src/main/resources/config.properties</tt> file.</p><div class="syntax"><div class="highlight"><pre><span class="nt">&lt;project&gt;</span>&#x000A;  <span class="nt">&lt;build&gt;</span>&#x00
 0A;    <span class="nt">&lt;plugins&gt;</span>&#x000A;      <span class="nt">&lt;plugin&gt;</span>&#x000A;        <span class="nt">&lt;groupId&gt;</span>org.apache.karaf.tooling<span class="nt">&lt;/groupId&gt;</span>&#x000A;        <span class="nt">&lt;artifactId&gt;</span>features-maven-plugin<span class="nt">&lt;/artifactId&gt;</span>&#x000A;        <span class="nt">&lt;version&gt;</span>2.3.0<span class="nt">&lt;/version&gt;</span>&#x000A;          <span class="nt">&lt;executions&gt;</span>&#x000A;            <span class="nt">&lt;execution&gt;</span>&#x000A;              <span class="nt">&lt;id&gt;</span>validate<span class="nt">&lt;/id&gt;</span>&#x000A;              <span class="nt">&lt;phase&gt;</span>process-resources<span class="nt">&lt;/phase&gt;</span>&#x000A;              <span class="nt">&lt;goals&gt;</span>&#x000A;                <span class="nt">&lt;goal&gt;</span>validate<span class="nt">&lt;/goal&gt;</span>&#x000A;              <span class="nt">&lt;/goals&gt;</span>
 &#x000A;              <span class="nt">&lt;configuration&gt;</span>&#x000A;                <span class="nt">&lt;file&gt;</span>target/features.xml<span class="nt">&lt;/file&gt;</span>&#x000A;                <span class="nt">&lt;karafConfig&gt;</span>src/main/resources/config.properties<span class="nt">&lt;/karafConfig&gt;</span>&#x000A;              <span class="nt">&lt;/configuration&gt;</span>&#x000A;            <span class="nt">&lt;/execution&gt;</span>&#x000A;          <span class="nt">&lt;/executions&gt;</span>&#x000A;          <span class="nt">&lt;dependencies&gt;</span>&#x000A;            <span class="nt">&lt;dependency&gt;</span>&#x000A;              <span class="nt">&lt;groupId&gt;</span>org.slf4j<span class="nt">&lt;/groupId&gt;</span>&#x000A;              <span class="nt">&lt;artifactId&gt;</span>slf4j-simple<span class="nt">&lt;/artifactId&gt;</span>&#x000A;              <span class="nt">&lt;version&gt;</span>1.4.3<span class="nt">&lt;/version&gt;</span>&#x000A;	        
 <span class="nt">&lt;/dependency&gt;</span>&#x000A;          <span class="nt">&lt;/dependencies&gt;</span>&#x000A;        <span class="nt">&lt;/plugin&gt;</span>&#x000A;    <span class="nt">&lt;/plugins&gt;</span>&#x000A;  <span class="nt">&lt;/build&gt;</span>  &#x000A;<span class="nt">&lt;/project&gt;</span>&#x000A;</pre></div>&#x000A;</div><h3 id="Parameters">Parameters</h3><div class="table-wrap"><table class="confluenceTable"><tr><th class="confluenceTh"> Name </th><th class="confluenceTh"> Type </th><th class="confluenceTh"> Description </th></tr><tr><td class="confluenceTd"> <tt>file</tt> </td><td class="confluenceTd"> <tt>File</tt> </td><td class="confluenceTd"> The features XML descriptor file to validate. <br/> Default value: <tt>/x1/asf/karaf-2.3.x/target/checkout/manual/target/classes/features.xml</tt> </td></tr><tr><td class="confluenceTd"> <tt>karafConfig</tt> </td><td class="confluenceTd"> <tt>String</tt> </td><td class="confluenceTd"> The Karaf <tt>config.properties<
 /tt> file to use during the validation process <br/> Default value: <tt>config.properties</tt> </td></tr><tr><td class="confluenceTd"> <tt>jreVersion</tt> </td><td class="confluenceTd"> <tt>String</tt> </td><td class="confluenceTd"> The JRE version that is used during the validation process <br/> Default value: {{jre-1.5}) </td></tr><tr><td class="confluenceTd"> <tt>karafVersion</tt> </td><td class="confluenceTd"> <tt>String</tt> </td><td class="confluenceTd"> The target Karaf version used to get the Karaf core features (standard and enterprise) <br/> Default value is the version of the plugin </td></tr><tr><td class="confluenceTd"> <tt>repositories</tt> </td><td class="confluenceTd"> <tt>String[]</tt> </td><td class="confluenceTd"> Additional features XML descriptors that will be used during the validation process </td></tr></table></div>
         </div>
       
           </div>
     <div id="siteFooter">
-      &copy; 2008-2012 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
+      &copy; 2008-2014 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
       <br/>
       Apache ServiceMix, ServiceMix, Apache, the Apache feather logo, and the Apache ServiceMix project logo are trademarks of The Apache Software Foundation.
     </div>

Modified: servicemix/site/production/docs/5.0.x/developers-guide/features-maven-plugin.html
URL: http://svn.apache.org/viewvc/servicemix/site/production/docs/5.0.x/developers-guide/features-maven-plugin.html?rev=1597941&r1=1597940&r2=1597941&view=diff
==============================================================================
--- servicemix/site/production/docs/5.0.x/developers-guide/features-maven-plugin.html (original)
+++ servicemix/site/production/docs/5.0.x/developers-guide/features-maven-plugin.html Wed May 28 08:20:15 2014
@@ -94,27 +94,12 @@
 </ul>
         </div>
         <div id="body">
-                              <h1 id="Usingthefeaturesmavenplugin">Using the features-maven-plugin</h1><p>The <tt>features-maven-plugin</tt> provides several goals to help you create and validate features XML descriptors as well as leverage your features to create a custom Karaf distribution.</p><div class="table-wrap"><table class="confluenceTable"><tr><th class="confluenceTh"> Goal </th><th class="confluenceTh"> Description </th></tr><tr><td class="confluenceTd"> <tt><a href="features-maven-plugin-add.html">features:add-features-to-repo</a></tt> </td><td class="confluenceTd"> Copies all the bundles required for a given set of features into a directory <br/> (e.g. for creating your own Karaf-based distribution) </td></tr><tr><td class="confluenceTd"> <tt>features:generate-features-file</tt> </td><td class="confluenceTd"> Deprecated - use <tt><a href="features-maven-plugin-generate.html">features:generate-features-xml</a></tt> instead </td></tr><tr><td class="confluenceTd"> <tt><a h
 ref="features-maven-plugin-generate.html">features:generate-features-xml</a></tt> </td><td class="confluenceTd"> Generates a features XML descriptor for a set of bundles </td></tr><tr><td class="confluenceTd"> <tt><a href="features-maven-plugin-validate.html">features:validate</a></tt> </td><td class="confluenceTd"> Validate a features XML descriptor by checking if all the required imports can be matched to exports </td></tr><tr><td class="confluenceTd"> {{</td><td class="confluenceTd">features:create-kar</td></tr></table></div><h2 id="Configurethefeaturesmavenplugin">Configure the features-maven-plugin</h2><p>In order to use the <tt>features-maven-plugin</tt>, you have to define the plugin in your project's <tt>pom.xml</tt> file:</p><div class="syntax"><pre name='code' class='brush: xml; gutter: false;'><code>
-&lt;project&gt;
-  &lt;build&gt;
-    &lt;plugins&gt;
-      &lt;plugin&gt;
-        &lt;groupId&gt;org.apache.karaf.tooling&lt;/groupId&gt;
-        &lt;artifactId&gt;features-maven-plugin&lt;/artifactId&gt;
-        &lt;version&gt;2.3.0&lt;/version&gt;
-
-        &lt;executions&gt;
-          &lt;!-- add execution definitions here --&gt;
-        &lt;/executions&gt;
-      &lt;/plugin&gt;
-    &lt;/plugins&gt;
-  &lt;/build&gt;  
-&lt;/project&gt;</code></pre></div>
+                              <h1 id="Usingthefeaturesmavenplugin">Using the features-maven-plugin</h1><p>The <tt>features-maven-plugin</tt> provides several goals to help you create and validate features XML descriptors as well as leverage your features to create a custom Karaf distribution.</p><div class="table-wrap"><table class="confluenceTable"><tr><th class="confluenceTh"> Goal </th><th class="confluenceTh"> Description </th></tr><tr><td class="confluenceTd"> <tt><a href="features-maven-plugin-add.html">features:add-features-to-repo</a></tt> </td><td class="confluenceTd"> Copies all the bundles required for a given set of features into a directory <br/> (e.g. for creating your own Karaf-based distribution) </td></tr><tr><td class="confluenceTd"> <tt>features:generate-features-file</tt> </td><td class="confluenceTd"> Deprecated - use <tt><a href="features-maven-plugin-generate.html">features:generate-features-xml</a></tt> instead </td></tr><tr><td class="confluenceTd"> <tt><a h
 ref="features-maven-plugin-generate.html">features:generate-features-xml</a></tt> </td><td class="confluenceTd"> Generates a features XML descriptor for a set of bundles </td></tr><tr><td class="confluenceTd"> <tt><a href="features-maven-plugin-validate.html">features:validate</a></tt> </td><td class="confluenceTd"> Validate a features XML descriptor by checking if all the required imports can be matched to exports </td></tr><tr><td class="confluenceTd"> {{</td><td class="confluenceTd">features:create-kar</td></tr></table></div><h2 id="Configurethefeaturesmavenplugin">Configure the features-maven-plugin</h2><p>In order to use the <tt>features-maven-plugin</tt>, you have to define the plugin in your project's <tt>pom.xml</tt> file:</p><div class="syntax"><div class="highlight"><pre><span class="nt">&lt;project&gt;</span>&#x000A;  <span class="nt">&lt;build&gt;</span>&#x000A;    <span class="nt">&lt;plugins&gt;</span>&#x000A;      <span class="nt">&lt;plugin&gt;</span>&#x000A;        
 <span class="nt">&lt;groupId&gt;</span>org.apache.karaf.tooling<span class="nt">&lt;/groupId&gt;</span>&#x000A;        <span class="nt">&lt;artifactId&gt;</span>features-maven-plugin<span class="nt">&lt;/artifactId&gt;</span>&#x000A;        <span class="nt">&lt;version&gt;</span>2.3.0<span class="nt">&lt;/version&gt;</span>&#x000A;&#x000A;        <span class="nt">&lt;executions&gt;</span>&#x000A;          <span class="c">&lt;!-- add execution definitions here --&gt;</span>&#x000A;        <span class="nt">&lt;/executions&gt;</span>&#x000A;      <span class="nt">&lt;/plugin&gt;</span>&#x000A;    <span class="nt">&lt;/plugins&gt;</span>&#x000A;  <span class="nt">&lt;/build&gt;</span>  &#x000A;<span class="nt">&lt;/project&gt;</span>&#x000A;</pre></div>&#x000A;</div>
         </div>
       
           </div>
     <div id="siteFooter">
-      &copy; 2008-2012 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
+      &copy; 2008-2014 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
       <br/>
       Apache ServiceMix, ServiceMix, Apache, the Apache feather logo, and the Apache ServiceMix project logo are trademarks of The Apache Software Foundation.
     </div>

Modified: servicemix/site/production/docs/5.0.x/developers-guide/github-contributions.html
URL: http://svn.apache.org/viewvc/servicemix/site/production/docs/5.0.x/developers-guide/github-contributions.html?rev=1597941&r1=1597940&r2=1597941&view=diff
==============================================================================
--- servicemix/site/production/docs/5.0.x/developers-guide/github-contributions.html (original)
+++ servicemix/site/production/docs/5.0.x/developers-guide/github-contributions.html Wed May 28 08:20:15 2014
@@ -133,7 +133,7 @@ git format-patch archon/trunk
       
           </div>
     <div id="siteFooter">
-      &copy; 2008-2012 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
+      &copy; 2008-2014 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
       <br/>
       Apache ServiceMix, ServiceMix, Apache, the Apache feather logo, and the Apache ServiceMix project logo are trademarks of The Apache Software Foundation.
     </div>

Modified: servicemix/site/production/docs/5.0.x/developers-guide/index.html
URL: http://svn.apache.org/viewvc/servicemix/site/production/docs/5.0.x/developers-guide/index.html?rev=1597941&r1=1597940&r2=1597941&view=diff
==============================================================================
--- servicemix/site/production/docs/5.0.x/developers-guide/index.html (original)
+++ servicemix/site/production/docs/5.0.x/developers-guide/index.html Wed May 28 08:20:15 2014
@@ -99,7 +99,7 @@
       
           </div>
     <div id="siteFooter">
-      &copy; 2008-2012 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
+      &copy; 2008-2014 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
       <br/>
       Apache ServiceMix, ServiceMix, Apache, the Apache feather logo, and the Apache ServiceMix project logo are trademarks of The Apache Software Foundation.
     </div>

Modified: servicemix/site/production/docs/5.0.x/developers-guide/shell-syntax.html
URL: http://svn.apache.org/viewvc/servicemix/site/production/docs/5.0.x/developers-guide/shell-syntax.html?rev=1597941&r1=1597940&r2=1597941&view=diff
==============================================================================
--- servicemix/site/production/docs/5.0.x/developers-guide/shell-syntax.html (original)
+++ servicemix/site/production/docs/5.0.x/developers-guide/shell-syntax.html Wed May 28 08:20:15 2014
@@ -178,7 +178,7 @@ karaf@root> $map
       
           </div>
     <div id="siteFooter">
-      &copy; 2008-2012 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
+      &copy; 2008-2014 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
       <br/>
       Apache ServiceMix, ServiceMix, Apache, the Apache feather logo, and the Apache ServiceMix project logo are trademarks of The Apache Software Foundation.
     </div>

Modified: servicemix/site/production/docs/5.0.x/developers-guide/toc.html
URL: http://svn.apache.org/viewvc/servicemix/site/production/docs/5.0.x/developers-guide/toc.html?rev=1597941&r1=1597940&r2=1597941&view=diff
==============================================================================
--- servicemix/site/production/docs/5.0.x/developers-guide/toc.html (original)
+++ servicemix/site/production/docs/5.0.x/developers-guide/toc.html Wed May 28 08:20:15 2014
@@ -123,7 +123,7 @@
       
           </div>
     <div id="siteFooter">
-      &copy; 2008-2012 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
+      &copy; 2008-2014 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
       <br/>
       Apache ServiceMix, ServiceMix, Apache, the Apache feather logo, and the Apache ServiceMix project logo are trademarks of The Apache Software Foundation.
     </div>

Modified: servicemix/site/production/docs/5.0.x/developers-guide/writing-tests.html
URL: http://svn.apache.org/viewvc/servicemix/site/production/docs/5.0.x/developers-guide/writing-tests.html?rev=1597941&r1=1597940&r2=1597941&view=diff
==============================================================================
--- servicemix/site/production/docs/5.0.x/developers-guide/writing-tests.html (original)
+++ servicemix/site/production/docs/5.0.x/developers-guide/writing-tests.html Wed May 28 08:20:15 2014
@@ -94,28 +94,12 @@
 </ul>
         </div>
         <div id="body">
-                              <h1 id="Writingintegrationtests">Writing integration tests</h1><p>We recommend using <a href="http://team.ops4j.org/wiki/display/paxexam/Pax+Exam">PAX Exam</a> to write integration tests when developing<br/>applications using Karaf.</p><p>Karaf provides an helper library to help writing such integration tests.</p><div class="syntax"><pre name='code' class='brush: java; gutter: false;'><code>
-   @Configuration
-   public static Option[] configuration() throws Exception{
-       return combine(
-           // Default karaf environment
-           Helper.getDefaultOptions(),
-           // Test on both equinox and felix
-           equinox(), felix()
-       );
-   }</code></pre></div><p>If you need to provision a few features in addition to the default Karaf environment, you can do so by adding the following code:</p><div class="syntax"><pre name='code' class='brush: java; gutter: false;'><code>
-           scanFeatures(
-                  maven().groupId(&quot;org.apache.felix.karaf&quot;)
-                         .artifactId(&quot;apache-felix-karaf&quot;)
-                         .type(&quot;xml&quot;).classifier(&quot;features&quot;)
-                         .versionAsInProject(),
-                  &quot;obr&quot;, &quot;wrapper&quot;
-           ),</code></pre></div>
+                              <h1 id="Writingintegrationtests">Writing integration tests</h1><p>We recommend using <a href="http://team.ops4j.org/wiki/display/paxexam/Pax+Exam">PAX Exam</a> to write integration tests when developing<br/>applications using Karaf.</p><p>Karaf provides an helper library to help writing such integration tests.</p><div class="syntax"><div class="highlight"><pre>   <span class="nd">@Configuration</span>&#x000A;   <span class="kd">public</span> <span class="kd">static</span> <span class="n">Option</span><span class="o">[]</span> <span class="nf">configuration</span><span class="o">()</span> <span class="kd">throws</span> <span class="n">Exception</span><span class="o">{</span>&#x000A;       <span class="k">return</span> <span class="nf">combine</span><span class="o">(</span>&#x000A;           <span class="c1">// Default karaf environment</span>&#x000A;           <span class="n">Helper</span><span class="o">.</span><span class="na">getDefaultOptions</span><
 span class="o">(),</span>&#x000A;           <span class="c1">// Test on both equinox and felix</span>&#x000A;           <span class="n">equinox</span><span class="o">(),</span> <span class="n">felix</span><span class="o">()</span>&#x000A;       <span class="o">);</span>&#x000A;   <span class="o">}</span>&#x000A;</pre></div>&#x000A;</div><p>If you need to provision a few features in addition to the default Karaf environment, you can do so by adding the following code:</p><div class="syntax"><div class="highlight"><pre>           <span class="n">scanFeatures</span><span class="o">(</span>&#x000A;                  <span class="n">maven</span><span class="o">().</span><span class="na">groupId</span><span class="o">(</span><span class="s">&quot;org.apache.felix.karaf&quot;</span><span class="o">)</span>&#x000A;                         <span class="o">.</span><span class="na">artifactId</span><span class="o">(</span><span class="s">&quot;apache-felix-karaf&quot;</span><span class="o">)</s
 pan>&#x000A;                         <span class="o">.</span><span class="na">type</span><span class="o">(</span><span class="s">&quot;xml&quot;</span><span class="o">).</span><span class="na">classifier</span><span class="o">(</span><span class="s">&quot;features&quot;</span><span class="o">)</span>&#x000A;                         <span class="o">.</span><span class="na">versionAsInProject</span><span class="o">(),</span>&#x000A;                  <span class="s">&quot;obr&quot;</span><span class="o">,</span> <span class="s">&quot;wrapper&quot;</span>&#x000A;           <span class="o">),</span>&#x000A;</pre></div>&#x000A;</div>
         </div>
       
           </div>
     <div id="siteFooter">
-      &copy; 2008-2012 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
+      &copy; 2008-2014 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
       <br/>
       Apache ServiceMix, ServiceMix, Apache, the Apache feather logo, and the Apache ServiceMix project logo are trademarks of The Apache Software Foundation.
     </div>

Modified: servicemix/site/production/docs/5.0.x/index.html
URL: http://svn.apache.org/viewvc/servicemix/site/production/docs/5.0.x/index.html?rev=1597941&r1=1597940&r2=1597941&view=diff
==============================================================================
--- servicemix/site/production/docs/5.0.x/index.html (original)
+++ servicemix/site/production/docs/5.0.x/index.html Wed May 28 08:20:15 2014
@@ -173,7 +173,7 @@
 
           </div>
     <div id="siteFooter">
-      &copy; 2008-2012 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
+      &copy; 2008-2014 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
       <br/>
       Apache ServiceMix, ServiceMix, Apache, the Apache feather logo, and the Apache ServiceMix project logo are trademarks of The Apache Software Foundation.
     </div>

Modified: servicemix/site/production/docs/5.0.x/karaf/index.html
URL: http://svn.apache.org/viewvc/servicemix/site/production/docs/5.0.x/karaf/index.html?rev=1597941&r1=1597940&r2=1597941&view=diff
==============================================================================
--- servicemix/site/production/docs/5.0.x/karaf/index.html (original)
+++ servicemix/site/production/docs/5.0.x/karaf/index.html Wed May 28 08:20:15 2014
@@ -147,7 +147,7 @@
       
           </div>
     <div id="siteFooter">
-      &copy; 2008-2012 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
+      &copy; 2008-2014 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
       <br/>
       Apache ServiceMix, ServiceMix, Apache, the Apache feather logo, and the Apache ServiceMix project logo are trademarks of The Apache Software Foundation.
     </div>

Modified: servicemix/site/production/docs/5.0.x/karaf/toc.html
URL: http://svn.apache.org/viewvc/servicemix/site/production/docs/5.0.x/karaf/toc.html?rev=1597941&r1=1597940&r2=1597941&view=diff
==============================================================================
--- servicemix/site/production/docs/5.0.x/karaf/toc.html (original)
+++ servicemix/site/production/docs/5.0.x/karaf/toc.html Wed May 28 08:20:15 2014
@@ -219,7 +219,7 @@
       
           </div>
     <div id="siteFooter">
-      &copy; 2008-2012 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
+      &copy; 2008-2014 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
       <br/>
       Apache ServiceMix, ServiceMix, Apache, the Apache feather logo, and the Apache ServiceMix project logo are trademarks of The Apache Software Foundation.
     </div>

Modified: servicemix/site/production/docs/5.0.x/quickstart/activemq.html
URL: http://svn.apache.org/viewvc/servicemix/site/production/docs/5.0.x/quickstart/activemq.html?rev=1597941&r1=1597940&r2=1597941&view=diff
==============================================================================
--- servicemix/site/production/docs/5.0.x/quickstart/activemq.html (original)
+++ servicemix/site/production/docs/5.0.x/quickstart/activemq.html Wed May 28 08:20:15 2014
@@ -89,64 +89,12 @@
 </ul>
         </div>
         <div id="body">
-                              <h1 id="AddingActiveMQtotheMix">Adding ActiveMQ to the 'Mix</h1><p>Out-of-the-box, every Apache ServiceMix instance comes with an embedded ActiveMQ JMS broker.  This makes it easy to communicate between Camel routes using persistent messages on the same machine, but it will also enable you to distribute your routes over multiple instances afterwards for clustering or load-balancing.</p><h2 id="Ourscenario">Our scenario</h2><p>In this scenario, we also want to move files between directories.  Instead of logging the move directly, we are going to send an event JMS message onto a queue.  Afterwards, we will create a second Camel route to receive the events and log them.</p><h2 id="Beforewestart">Before we start</h2><p>First, we have to install an optional feature to allow Camel send and receive JMS messages.  We'll talk about optional features a bit more in the next page of this quickstart guide, but for now, just run the following command in the console.<
 /p><div class="syntax"><pre name='code' class='brush: text; gutter: false;'><code>
-karaf@root&gt; features:install camel-jms</code></pre></div><h2 id="Movingfilesandsendingeventmessages">Moving files and sending event messages</h2><p>The first Blueprint XML file we'll create contains a Camel route that moves the files from <tt>activemq/input</tt> to the <tt>activemq/output</tt> directory.  Afterwards, it will generate an event message and send that to an ActiveMQ queue called <tt>events</tt>.</p><div class="syntax"><pre name='code' class='brush: xml; gutter: false;'><code>
-&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
-&lt;blueprint
-    xmlns=&quot;http://www.osgi.org/xmlns/blueprint/v1.0.0&quot;
-    xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
-    xsi:schemaLocation=&quot;
-      http://www.osgi.org/xmlns/blueprint/v1.0.0
-      http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd&quot;&gt;
-
-    &lt;camelContext xmlns=&quot;http://camel.apache.org/schema/blueprint&quot;&gt;
-      &lt;route&gt;
-        &lt;from uri=&quot;file:activemq/input&quot;/&gt;
-        &lt;to uri=&quot;file:activemq/output&quot;/&gt;
-
-        &lt;setBody&gt;
-          &lt;simple&gt;
-            FileMovedEvent(file: ${file:name}, timestamp: ${date:now:hh:MM:ss.SSS})
-          &lt;/simple&gt;
-        &lt;/setBody&gt;
-        &lt;to uri=&quot;activemq://events&quot; /&gt;
-      &lt;/route&gt;
-    &lt;/camelContext&gt;
-
-    &lt;bean id=&quot;activemq&quot; class=&quot;org.apache.activemq.camel.component.ActiveMQComponent&quot;&gt;
-        &lt;property name=&quot;brokerURL&quot; value=&quot;tcp://localhost:61616&quot;/&gt;
-    	&lt;property name=&quot;userName&quot; value=&quot;smx&quot;/&gt;
-    	&lt;property name=&quot;password&quot; value=&quot;smx&quot;/&gt;
-    &lt;/bean&gt;
-
-&lt;/blueprint&gt;</code></pre></div><p>Save this file in ServiceMix' <tt>deploy</tt> folder and use <tt>osgi:list</tt> to check on the bundle status as you did with the simple Camel example.  You should now be able to put files in the <tt>activemq/input</tt> directory and see them being moved to <tt>activemq/output</tt>.</p><h2 id="Receivingtheeventmessages">Receiving the event messages</h2><p>After deploying the first XML file, you're obviously not seeing any events being logged yet.  The event messages are sent to an ActiveMQ queue, but there's nobody to receive the events yet.  Let's change that now by creating a second Blueprint XML file.</p><div class="syntax"><pre name='code' class='brush: xml; gutter: false;'><code>
-&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
-&lt;blueprint
-    xmlns=&quot;http://www.osgi.org/xmlns/blueprint/v1.0.0&quot;
-    xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
-    xsi:schemaLocation=&quot;
-      http://www.osgi.org/xmlns/blueprint/v1.0.0
-      http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd&quot;&gt;
-
-    &lt;camelContext xmlns=&quot;http://camel.apache.org/schema/blueprint&quot;&gt;
-      &lt;route&gt;
-        &lt;from uri=&quot;activemq://events&quot;/&gt;
-        &lt;to uri=&quot;log:events&quot;/&gt;
-      &lt;/route&gt;
-    &lt;/camelContext&gt;
-
-    &lt;bean id=&quot;activemq&quot; class=&quot;org.apache.activemq.camel.component.ActiveMQComponent&quot;&gt;
-        &lt;property name=&quot;brokerURL&quot; value=&quot;tcp://localhost:61616&quot;/&gt;
-    	&lt;property name=&quot;userName&quot; value=&quot;smx&quot;/&gt;
-    	&lt;property name=&quot;password&quot; value=&quot;smx&quot;/&gt;
-    &lt;/bean&gt;
-
-&lt;/blueprint&gt;</code></pre></div><p>As soon as this second file has been deployed, you'll start seeing the event messages in your <tt>log:display</tt> output.</p><h2 id="Usingtheshelltomanagetheroutes">Using the shell to manage the routes</h2><p>You can now start and stop both routes from the command shell.  The important thing to note here is that you can stop the event handler route while files are being processed.  As soon as you restart that bundle afterwards, you'll receive the events from all files that have been moved while the route was not running.</p>
+                              <h1 id="AddingActiveMQtotheMix">Adding ActiveMQ to the 'Mix</h1><p>Out-of-the-box, every Apache ServiceMix instance comes with an embedded ActiveMQ JMS broker.  This makes it easy to communicate between Camel routes using persistent messages on the same machine, but it will also enable you to distribute your routes over multiple instances afterwards for clustering or load-balancing.</p><h2 id="Ourscenario">Our scenario</h2><p>In this scenario, we also want to move files between directories.  Instead of logging the move directly, we are going to send an event JMS message onto a queue.  Afterwards, we will create a second Camel route to receive the events and log them.</p><h2 id="Movingfilesandsendingeventmessages">Moving files and sending event messages</h2><p>The first Blueprint XML file we'll create contains a Camel route that moves the files from <tt>activemq/input</tt> to the <tt>activemq/output</tt> directory.  Afterwards, it will generate an event 
 message and send that to an ActiveMQ queue called <tt>events</tt>.</p><div class="syntax"><div class="highlight"><pre><span class="cp">&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;</span>&#x000A;<span class="nt">&lt;blueprint</span>&#x000A;    <span class="na">xmlns=</span><span class="s">&quot;http://www.osgi.org/xmlns/blueprint/v1.0.0&quot;</span>&#x000A;    <span class="na">xmlns:xsi=</span><span class="s">&quot;http://www.w3.org/2001/XMLSchema-instance&quot;</span>&#x000A;    <span class="na">xsi:schemaLocation=</span><span class="s">&quot;</span>&#x000A;<span class="s">      http://www.osgi.org/xmlns/blueprint/v1.0.0</span>&#x000A;<span class="s">      http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd&quot;</span><span class="nt">&gt;</span>&#x000A;&#x000A;    <span class="nt">&lt;camelContext</span> <span class="na">xmlns=</span><span class="s">&quot;http://camel.apache.org/schema/blueprint&quot;</span><span class="nt">&gt;</span>&#x000A;      <span c
 lass="nt">&lt;route&gt;</span>&#x000A;        <span class="nt">&lt;from</span> <span class="na">uri=</span><span class="s">&quot;file:activemq/input&quot;</span><span class="nt">/&gt;</span>&#x000A;        <span class="nt">&lt;to</span> <span class="na">uri=</span><span class="s">&quot;file:activemq/output&quot;</span><span class="nt">/&gt;</span>&#x000A;&#x000A;        <span class="nt">&lt;setBody&gt;</span>&#x000A;          <span class="nt">&lt;simple&gt;</span>&#x000A;            FileMovedEvent(file: ${file:name}, timestamp: ${date:now:hh:MM:ss.SSS})&#x000A;          <span class="nt">&lt;/simple&gt;</span>&#x000A;        <span class="nt">&lt;/setBody&gt;</span>&#x000A;        <span class="nt">&lt;to</span> <span class="na">uri=</span><span class="s">&quot;activemq://events&quot;</span> <span class="nt">/&gt;</span>&#x000A;      <span class="nt">&lt;/route&gt;</span>&#x000A;    <span class="nt">&lt;/camelContext&gt;</span>&#x000A;<span class="nt">&lt;/blueprint&gt;</span>&#x000A;<
 /pre></div>&#x000A;</div><p>Save this file in ServiceMix' <tt>deploy</tt> folder and use <tt>osgi:list</tt> to check on the bundle status as you did with the simple Camel example.  You should now be able to put files in the <tt>activemq/input</tt> directory and see them being moved to <tt>activemq/output</tt>.</p><h2 id="Receivingtheeventmessages">Receiving the event messages</h2><p>After deploying the first XML file, you're obviously not seeing any events being logged yet.  The event messages are sent to an ActiveMQ queue, but there's nobody to receive the events yet.  Let's change that now by creating a second Blueprint XML file.</p><div class="syntax"><div class="highlight"><pre><span class="cp">&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;</span>&#x000A;<span class="nt">&lt;blueprint</span>&#x000A;    <span class="na">xmlns=</span><span class="s">&quot;http://www.osgi.org/xmlns/blueprint/v1.0.0&quot;</span>&#x000A;    <span class="na">xmlns:xsi=</span><span cl
 ass="s">&quot;http://www.w3.org/2001/XMLSchema-instance&quot;</span>&#x000A;    <span class="na">xsi:schemaLocation=</span><span class="s">&quot;</span>&#x000A;<span class="s">      http://www.osgi.org/xmlns/blueprint/v1.0.0</span>&#x000A;<span class="s">      http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd&quot;</span><span class="nt">&gt;</span>&#x000A;&#x000A;    <span class="nt">&lt;camelContext</span> <span class="na">xmlns=</span><span class="s">&quot;http://camel.apache.org/schema/blueprint&quot;</span><span class="nt">&gt;</span>&#x000A;      <span class="nt">&lt;route&gt;</span>&#x000A;        <span class="nt">&lt;from</span> <span class="na">uri=</span><span class="s">&quot;activemq://events&quot;</span><span class="nt">/&gt;</span>&#x000A;        <span class="nt">&lt;to</span> <span class="na">uri=</span><span class="s">&quot;log:events&quot;</span><span class="nt">/&gt;</span>&#x000A;      <span class="nt">&lt;/route&gt;</span>&#x000A;    <span class="nt">&lt;/c
 amelContext&gt;</span>&#x000A;<span class="nt">&lt;/blueprint&gt;</span>&#x000A;</pre></div>&#x000A;</div><p>As soon as this second file has been deployed, you'll start seeing the event messages in your <tt>log:display</tt> output.</p><h2 id="Usingtheshelltomanagetheroutes">Using the shell to manage the routes</h2><p>You can now start and stop both routes from the command shell.  The important thing to note here is that you can stop the event handler route while files are being processed.  As soon as you restart that bundle afterwards, you'll receive the events from all files that have been moved while the route was not running.</p>
         </div>
       
           </div>
     <div id="siteFooter">
-      &copy; 2008-2012 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
+      &copy; 2008-2014 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
       <br/>
       Apache ServiceMix, ServiceMix, Apache, the Apache feather logo, and the Apache ServiceMix project logo are trademarks of The Apache Software Foundation.
     </div>

Modified: servicemix/site/production/docs/5.0.x/quickstart/camel.html
URL: http://svn.apache.org/viewvc/servicemix/site/production/docs/5.0.x/quickstart/camel.html?rev=1597941&r1=1597940&r2=1597941&view=diff
==============================================================================
--- servicemix/site/production/docs/5.0.x/quickstart/camel.html (original)
+++ servicemix/site/production/docs/5.0.x/quickstart/camel.html Wed May 28 08:20:15 2014
@@ -89,31 +89,12 @@
 </ul>
         </div>
         <div id="body">
-                              <h1 id="UsingCamel">Using Camel</h1><p>Now that we know how to operate Apache ServiceMix through the shell console, it's time to start using it for what it is built for.  Let's build our very first integration solution with a Camel route and deploy it on ServiceMix.</p><h2 id="Oursimplescenario">Our simple scenario</h2><p>In this simple scenario, we're going to move files from an input directory called <tt>camel/input</tt> to an output directory called <tt>camel/output</tt>.  To ensure we can keep track of which files get moved, we'll also write a message to the log file whenever we move a file.</p><h2 id="Creatingtheroute">Creating the route</h2><p>One of the most simple ways to deploy a new route on ServiceMix, is by defining the route in a Blueprint XML file.</p><div class="syntax"><pre name='code' class='brush: xml; gutter: false;'><code>
-&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
-&lt;blueprint
-    xmlns=&quot;http://www.osgi.org/xmlns/blueprint/v1.0.0&quot;
-    xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
-    xsi:schemaLocation=&quot;
-      http://www.osgi.org/xmlns/blueprint/v1.0.0
-      http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd&quot;&gt;
-
-    &lt;camelContext xmlns=&quot;http://camel.apache.org/schema/blueprint&quot;&gt;
-      &lt;route&gt;
-        &lt;from uri=&quot;file:camel/input&quot;/&gt;
-        &lt;log message=&quot;Moving ${file:name} to the output directory&quot;/&gt;
-        &lt;to uri=&quot;file:camel/output&quot;/&gt;
-      &lt;/route&gt;
-    &lt;/camelContext&gt;
-
-&lt;/blueprint&gt;</code></pre></div><h2 id="Deployingtheroute">Deploying the route</h2><p>In order to deploy and start the route, just copy the XML file you created into ServiceMix' <tt>deploy</tt> directory.  The file will get picked up and deployed by ServiceMix.  You will see a <tt>camel/input</tt> folder appear in your ServiceMix installation directory and any files you copy into that directory will get moved into the <tt>camel/output</tt> directory.</p><p>If you do a <tt>log:display</tt> in the shell, you will also see the log output for every file that's been moved.</p><p><img border="0" src="images/camel-sample-log.png"/></p><h2 id="Usingtheshelltomanagetheroute">Using the shell to manage the route</h2><p>Using <tt>osgi:list</tt>, you'll notice that your XML file has been transformed into a bundle and that the Blueprint container has been created to start your Camel route.</p><p><img border="0" src="images/camel-sample-deploy.png"/></p><p>From this output, you also learn tha
 t the bundle id for your XML file is 200.  This allow you to start and stop the route whenever necessary.  Let's give this a go now...</p><p>First, stop the route with</p><div class="syntax"><pre name='code' class='brush: text; gutter: false;'><code>
-karaf@root&gt; osgi:stop 200</code></pre></div><p>The route is no longer active, so any files you copy into the <tt>orders/input</tt> folder will remain there for now.  As soon as you restart the route, the pending files will get moving again.</p><div class="syntax"><pre name='code' class='brush: text; gutter: false;'><code>
-karaf@root&gt; osgi:start 200</code></pre></div>
+                              <h1 id="UsingCamel">Using Camel</h1><p>Now that we know how to operate Apache ServiceMix through the shell console, it's time to start using it for what it is built for.  Let's build our very first integration solution with a Camel route and deploy it on ServiceMix.</p><h2 id="Oursimplescenario">Our simple scenario</h2><p>In this simple scenario, we're going to move files from an input directory called <tt>camel/input</tt> to an output directory called <tt>camel/output</tt>.  To ensure we can keep track of which files get moved, we'll also write a message to the log file whenever we move a file.</p><h2 id="Creatingtheroute">Creating the route</h2><p>One of the most simple ways to deploy a new route on ServiceMix, is by defining the route in a Blueprint XML file.</p><div class="syntax"><div class="highlight"><pre><span class="cp">&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;</span>&#x000A;<span class="nt">&lt;blueprint</span>&#x000A;  
   <span class="na">xmlns=</span><span class="s">&quot;http://www.osgi.org/xmlns/blueprint/v1.0.0&quot;</span>&#x000A;    <span class="na">xmlns:xsi=</span><span class="s">&quot;http://www.w3.org/2001/XMLSchema-instance&quot;</span>&#x000A;    <span class="na">xsi:schemaLocation=</span><span class="s">&quot;</span>&#x000A;<span class="s">      http://www.osgi.org/xmlns/blueprint/v1.0.0</span>&#x000A;<span class="s">      http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd&quot;</span><span class="nt">&gt;</span>&#x000A;&#x000A;    <span class="nt">&lt;camelContext</span> <span class="na">xmlns=</span><span class="s">&quot;http://camel.apache.org/schema/blueprint&quot;</span><span class="nt">&gt;</span>&#x000A;      <span class="nt">&lt;route&gt;</span>&#x000A;        <span class="nt">&lt;from</span> <span class="na">uri=</span><span class="s">&quot;file:camel/input&quot;</span><span class="nt">/&gt;</span>&#x000A;        <span class="nt">&lt;log</span> <span class="na">message=<
 /span><span class="s">&quot;Moving ${file:name} to the output directory&quot;</span><span class="nt">/&gt;</span>&#x000A;        <span class="nt">&lt;to</span> <span class="na">uri=</span><span class="s">&quot;file:camel/output&quot;</span><span class="nt">/&gt;</span>&#x000A;      <span class="nt">&lt;/route&gt;</span>&#x000A;    <span class="nt">&lt;/camelContext&gt;</span>&#x000A;&#x000A;<span class="nt">&lt;/blueprint&gt;</span>&#x000A;</pre></div>&#x000A;</div><h2 id="Deployingtheroute">Deploying the route</h2><p>In order to deploy and start the route, just copy the XML file you created into ServiceMix' <tt>deploy</tt> directory.  The file will get picked up and deployed by ServiceMix.  You will see a <tt>camel/input</tt> folder appear in your ServiceMix installation directory and any files you copy into that directory will get moved into the <tt>camel/output</tt> directory.</p><p>If you do a <tt>log:display</tt> in the shell, you will also see the log output for every file tha
 t's been moved.</p><p><img border="0" src="images/camel-sample-log.png"/></p><h2 id="Usingtheshelltomanagetheroute">Using the shell to manage the route</h2><p>Using <tt>osgi:list</tt>, you'll notice that your XML file has been transformed into a bundle and that the Blueprint container has been created to start your Camel route.</p><p><img border="0" src="images/camel-sample-deploy.png"/></p><p>From this output, you also learn that the bundle id for your XML file is 200.  This allow you to start and stop the route whenever necessary.  Let's give this a go now...</p><p>First, stop the route with</p><div class="syntax"><div class="highlight"><pre>karaf@root&gt; osgi:stop 200&#x000A;</pre></div>&#x000A;</div><p>The route is no longer active, so any files you copy into the <tt>orders/input</tt> folder will remain there for now.  As soon as you restart the route, the pending files will get moving again.</p><div class="syntax"><div class="highlight"><pre>karaf@root&gt; osgi:start 200&#x000
 A;</pre></div>&#x000A;</div>
         </div>
       
           </div>
     <div id="siteFooter">
-      &copy; 2008-2012 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
+      &copy; 2008-2014 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
       <br/>
       Apache ServiceMix, ServiceMix, Apache, the Apache feather logo, and the Apache ServiceMix project logo are trademarks of The Apache Software Foundation.
     </div>

Modified: servicemix/site/production/docs/5.0.x/quickstart/console.html
URL: http://svn.apache.org/viewvc/servicemix/site/production/docs/5.0.x/quickstart/console.html?rev=1597941&r1=1597940&r2=1597941&view=diff
==============================================================================
--- servicemix/site/production/docs/5.0.x/quickstart/console.html (original)
+++ servicemix/site/production/docs/5.0.x/quickstart/console.html Wed May 28 08:20:15 2014
@@ -89,19 +89,12 @@
 </ul>
         </div>
         <div id="body">
-                              <h1 id="ApacheServiceMixconsole">Apache ServiceMix console</h1><p>Now that we successfully installed and started Apache ServiceMix, we'll take a closer look at the console.  This is where you manage your ServiceMix instance, add and remove bundles, install optional features, ...</p><h2 id="Workingwithbundles">Working with bundles</h2><p>When ServiceMix is first started, a whole set of bundles providing the core features for the product are being installed.  Let's use the command console to find out more about them...</p><p>The <tt>osgi:list</tt> command can be used to get a list of all bundles currently installed.  Enter this</p><div class="syntax"><pre name='code' class='brush: text; gutter: false;'><code>
-karaf@root&gt; osgi:list</code></pre></div><p>This is what the output looks like if you run this on your ServiceMix instance.</p><p>!/quickstart/images/osgi-list.png</p>|title=osgi:list!<p>For every bundle, you see:</p><ul><li><p>the bundle id</p></li><li><p>the bundle state</p></li><li><p>if the bundle contains a Blueprint or Spring XML file, the next 2 columns will show you if the beans defined there were created successfully</p></li><li><p>the bundle start level</p></li><li><p>the bundle name and version</p></li></ul><p>If you're looking for something specific in the list, you can use unix-like pipes and utilities to help you.  An example: to look for all Camel related bundles...</p><div class="syntax"><pre name='code' class='brush: text; gutter: false;'><code>
-karaf@root&gt; osgi:list | grep camel</code></pre></div><p>!/quickstart/images/osgi-list-pipegrep.png</p>|title=osgi:list!<h2 id="Workingwithlogging">Working with logging</h2><p>Many of the applications you write will have some form of log output.  To look at the message in the log file, you can us the <tt>log:diplay</tt> command.</p><div class="syntax"><pre name='code' class='brush: text; gutter: false;'><code>
-karaf@root&gt; log:display</code></pre></div><p>!/quickstart/images/log-display.png</p>|title=log:display!<p>If you're only interested in the latest exception in the log file, you can use <tt>log:display-exception</tt> instead.</p><div class="syntax"><pre name='code' class='brush: text; gutter: false;'><code>
-karaf@root&gt; log:display-exception</code></pre></div><p>!/quickstart/images/log-display-exception.png</p>|title=log:display-exception!<p>You can also change the log level at runtime by using the <tt>log:set</tt> command.  You can try these commands on your instance now by first setting the log level to <tt>DEBUG</tt> and then using <tt>grep</tt> to make sure that you can actually see the extra logging.</p><div class="syntax"><pre name='code' class='brush: text; gutter: false;'><code>
-karaf@root&gt; log:set DEBUG
-karaf@root&gt; log:display | grep DEBUG</code></pre></div><p>!/quickstart/images/log-set-debug.png</p>|title=log:set DEBUG!<p>Afterwards, revert the log level to its original <tt>INFO</tt> value again with <tt>log:set</tt>.</p><div class="syntax"><pre name='code' class='brush: text; gutter: false;'><code>
-karaf@root&gt; log:set INFO</code></pre></div><h2 id="...andtheresalotmore">...and there's a lot more</h2><p>These are obviously just a few examples of what the command shell is all about.  There are a lot more commands in the shell to help you deploy, monitor, manage and troubleshoot the applications you're building with ServiceMix.</p>
+                              <h1 id="ApacheServiceMixconsole">Apache ServiceMix console</h1><p>Now that we successfully installed and started Apache ServiceMix, we'll take a closer look at the console.  This is where you manage your ServiceMix instance, add and remove bundles, install optional features, ...</p><h2 id="Workingwithbundles">Working with bundles</h2><p>When ServiceMix is first started, a whole set of bundles providing the core features for the product are being installed.  Let's use the command console to find out more about them...</p><p>The <tt>osgi:list</tt> command can be used to get a list of all bundles currently installed.  Enter this</p><div class="syntax"><div class="highlight"><pre>karaf@root&gt; osgi:list&#x000A;</pre></div>&#x000A;</div><p>This is what the output looks like if you run this on your ServiceMix instance.</p><p>!/quickstart/images/osgi-list.png</p>|title=osgi:list!<p>For every bundle, you see:</p><ul><li><p>the bundle id</p></li><li><p>the bund
 le state</p></li><li><p>if the bundle contains a Blueprint or Spring XML file, the next 2 columns will show you if the beans defined there were created successfully</p></li><li><p>the bundle start level</p></li><li><p>the bundle name and version</p></li></ul><p>If you're looking for something specific in the list, you can use unix-like pipes and utilities to help you.  An example: to look for all Camel related bundles...</p><div class="syntax"><div class="highlight"><pre>karaf@root&gt; osgi:list | grep camel&#x000A;</pre></div>&#x000A;</div><p>!/quickstart/images/osgi-list-pipegrep.png</p>|title=osgi:list!<h2 id="Workingwithlogging">Working with logging</h2><p>Many of the applications you write will have some form of log output.  To look at the message in the log file, you can us the <tt>log:diplay</tt> command.</p><div class="syntax"><div class="highlight"><pre>karaf@root&gt; log:display&#x000A;</pre></div>&#x000A;</div><p>!/quickstart/images/log-display.png</p>|title=log:display!<
 p>If you're only interested in the latest exception in the log file, you can use <tt>log:display-exception</tt> instead.</p><div class="syntax"><div class="highlight"><pre>karaf@root&gt; log:display-exception&#x000A;</pre></div>&#x000A;</div><p>!/quickstart/images/log-display-exception.png</p>|title=log:display-exception!<p>You can also change the log level at runtime by using the <tt>log:set</tt> command.  You can try these commands on your instance now by first setting the log level to <tt>DEBUG</tt> and then using <tt>grep</tt> to make sure that you can actually see the extra logging.</p><div class="syntax"><div class="highlight"><pre>karaf@root&gt; log:set DEBUG&#x000A;karaf@root&gt; log:display | grep DEBUG&#x000A;</pre></div>&#x000A;</div><p>!/quickstart/images/log-set-debug.png</p>|title=log:set DEBUG!<p>Afterwards, revert the log level to its original <tt>INFO</tt> value again with <tt>log:set</tt>.</p><div class="syntax"><div class="highlight"><pre>karaf@root&gt; log:set IN
 FO&#x000A;</pre></div>&#x000A;</div><h2 id="...andtheresalotmore">...and there's a lot more</h2><p>These are obviously just a few examples of what the command shell is all about.  There are a lot more commands in the shell to help you deploy, monitor, manage and troubleshoot the applications you're building with ServiceMix.</p>
         </div>
       
           </div>
     <div id="siteFooter">
-      &copy; 2008-2012 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
+      &copy; 2008-2014 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
       <br/>
       Apache ServiceMix, ServiceMix, Apache, the Apache feather logo, and the Apache ServiceMix project logo are trademarks of The Apache Software Foundation.
     </div>

Modified: servicemix/site/production/docs/5.0.x/quickstart/features.html
URL: http://svn.apache.org/viewvc/servicemix/site/production/docs/5.0.x/quickstart/features.html?rev=1597941&r1=1597940&r2=1597941&view=diff
==============================================================================
--- servicemix/site/production/docs/5.0.x/quickstart/features.html (original)
+++ servicemix/site/production/docs/5.0.x/quickstart/features.html Wed May 28 08:20:15 2014
@@ -89,15 +89,12 @@
 </ul>
         </div>
         <div id="body">
-                              <h1 id="Optionalfeatures">Optional features</h1><p>Everything discussed in the quickstart guide so far is installed out-of-the-box in Apache ServiceMix, but we also have a lot of optional features that can be installed in the container when necessary.</p><h2 id="Listoffeatures">List of features</h2><p>The list of features is available with the <tt>features:list</tt> command.  The overview shows you whether or not the feature is currently installed, the version and the name of the feature.</p><p><img border="0" src="images/featureslist.png"/></p><p>The full list contains a lot of different features: optional Camel components, features for adding OBR or wrapper support to Serviceix, a web console, ...  Again, you can use things like {{</p>|}} and <tt>grep</tt> to find the things in the list that you're interested in.<div class="syntax"><pre name='code' class='brush: text; gutter: false;'><code>
-karaf@root&gt; features:list | grep camel</code></pre></div><h2 id="ExampleWebconsole">Example: Web console</h2><p>To get the web console installed in ServiceMix, install the feature from your console</p><div class="syntax"><pre name='code' class='brush: text; gutter: false;'><code>
-karaf@root&gt; features:install webconsole</code></pre></div><p>Afterwards, you can verify that the feature is marked installed in the overview.  You'll notice that the <tt>webconsole-base</tt> feature has also been installed as a requirement for the <tt>webconsole</tt> feature itself.</p><div class="syntax"><pre name='code' class='brush: text; gutter: false;'><code>
-karaf@root&gt; features:list | grep webconsole</code></pre></div><p><img border="0" src="images/featureslist-grep-webconsole.png"/></p><p>You will now be able to point your browser to http://localhost:8181/system/console and login with user <tt>smx</tt> and password <tt>smx</tt> to access the web console.  From the webconsole, you can also start and stop bundles, install optional features again, ...</p>
+                              <h1 id="Optionalfeatures">Optional features</h1><p>Everything discussed in the quickstart guide so far is installed out-of-the-box in Apache ServiceMix, but we also have a lot of optional features that can be installed in the container when necessary.</p><h2 id="Listoffeatures">List of features</h2><p>The list of features is available with the <tt>features:list</tt> command.  The overview shows you whether or not the feature is currently installed, the version and the name of the feature.</p><p><img border="0" src="images/featureslist.png"/></p><p>The full list contains a lot of different features: optional Camel components, features for adding OBR or wrapper support to Serviceix, a web console, ...  Again, you can use things like {{</p>|}} and <tt>grep</tt> to find the things in the list that you're interested in.<div class="syntax"><div class="highlight"><pre>karaf@root&gt; features:list | grep camel&#x000A;</pre></div>&#x000A;</div><h2 id="ExampleWeb
 console">Example: Web console</h2><p>To get the web console installed in ServiceMix, install the feature from your console</p><div class="syntax"><div class="highlight"><pre>karaf@root&gt; features:install webconsole&#x000A;</pre></div>&#x000A;</div><p>Afterwards, you can verify that the feature is marked installed in the overview.  You'll notice that the <tt>webconsole-base</tt> feature has also been installed as a requirement for the <tt>webconsole</tt> feature itself.</p><div class="syntax"><div class="highlight"><pre>karaf@root&gt; features:list | grep webconsole&#x000A;</pre></div>&#x000A;</div><p><img border="0" src="images/featureslist-grep-webconsole.png"/></p><p>You will now be able to point your browser to http://localhost:8181/system/console and login with user <tt>smx</tt> and password <tt>smx</tt> to access the web console.  From the webconsole, you can also start and stop bundles, install optional features again, ...</p>
         </div>
       
           </div>
     <div id="siteFooter">
-      &copy; 2008-2012 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
+      &copy; 2008-2014 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
       <br/>
       Apache ServiceMix, ServiceMix, Apache, the Apache feather logo, and the Apache ServiceMix project logo are trademarks of The Apache Software Foundation.
     </div>

Modified: servicemix/site/production/docs/5.0.x/quickstart/index.html
URL: http://svn.apache.org/viewvc/servicemix/site/production/docs/5.0.x/quickstart/index.html?rev=1597941&r1=1597940&r2=1597941&view=diff
==============================================================================
--- servicemix/site/production/docs/5.0.x/quickstart/index.html (original)
+++ servicemix/site/production/docs/5.0.x/quickstart/index.html Wed May 28 08:20:15 2014
@@ -94,7 +94,7 @@
       
           </div>
     <div id="siteFooter">
-      &copy; 2008-2012 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
+      &copy; 2008-2014 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
       <br/>
       Apache ServiceMix, ServiceMix, Apache, the Apache feather logo, and the Apache ServiceMix project logo are trademarks of The Apache Software Foundation.
     </div>

Modified: servicemix/site/production/docs/5.0.x/quickstart/installation.html
URL: http://svn.apache.org/viewvc/servicemix/site/production/docs/5.0.x/quickstart/installation.html?rev=1597941&r1=1597940&r2=1597941&view=diff
==============================================================================
--- servicemix/site/production/docs/5.0.x/quickstart/installation.html (original)
+++ servicemix/site/production/docs/5.0.x/quickstart/installation.html Wed May 28 08:20:15 2014
@@ -89,16 +89,12 @@
 </ul>
         </div>
         <div id="body">
-                              <h1 id="Installation">Installation</h1><p>Before we can start working with Apache ServiceMix, we have to get it installed and running on our local machine first.</p><h2 id="Systemrequirements">System requirements</h2><p>For running Apache ServiceMix itself, you'll need</p><ul><li><p>Java Runtime Environment (JRE) 1.6.x (Java 6) or<br/>  Java Runtime Environment (JRE) 1.7.x (Java 7)</p></li><li><p>About 100 MB of free disk space for the default assembly</p></li></ul><p>If you're developing your own integration applications and OSGi bundles, you'll also need</p><ul><li><p>Java Developer Kit (JDK) 1.6.x (Java 6) or<br/>  Java Developer Kit (JDK) 1.7.x (Java 7)</p></li><li><p>Apache Maven 3.0.4 or higher</p></li></ul><h2 id="DownloadingApacheServiceMix">Downloading Apache ServiceMix</h2><p>Apache ServiceMix 5.0.0-SNAPSHOT is available under the Apache License v2 and can be downloaded from <a href="http://servicemix.apache.org/downloads.html">http://servicem
 ix.apache.org/downloads.html</a>.</p><p>Depending on your operation system, you should download either the tar.gz or the zip file:</p><ul><li><p><tt>tar.gz</tt> for Linux/Unix/MacOS X</p></li><li><p><tt>zip</tt> for Windows</p></li></ul><h2 id="InstallingApacheServiceMix">Installing Apache ServiceMix</h2><p>Installing Apache ServiceMix is as simple as uncompressing the downloaded archive on your hard disk.  For the rest of this guide, we'll refer to the this location as <strong><tt>&lt;SERVICEMIX_HOME></tt></strong>.</p><h2 id="StartingApacheServiceMix">Starting Apache ServiceMix</h2><p>Depending on your platform, start Apache ServiceMix by following the instructions below.  After starting the container, you will have access to the console from which you can manage the container.</p><h3 id="OnWindows">On Windows</h3><p>In a command prompt window, navigate to the directory where you extracted ServiceMix and run the <tt>bin\servicemix.bat</tt> file.</p><p>Example: if ServiceMix in ins
 talled in the <tt>c:\tools\apache-servicemix-5.0.0-SNAPSHOT</tt> directory</p><div class="syntax"><pre name='code' class='brush: bat; gutter: false;'><code>
-&gt; cd c:\tools\apache-servicemix-5.0.0-SNAPSHOT
-&gt; .\bin\servicemix</code></pre></div><p><img border="0" src="images/start-windows.png"/></p><h3 id="OnLinuxUnixMacOSX">On Linux/Unix/MacOS X</h3><p>On a command shell, navigate to the directory where you extracted ServiceMix and the <tt>bin/servicemix</tt> shell script</p><p>Example: if ServiceMix is installed in the <tt>~/Applications/apache-servicemix-5.0.0-SNAPSHOT</tt> directory.</p><div class="syntax"><pre name='code' class='brush: bash; gutter: false;'><code>
-$ cd ~/Applications/apache-servicemix-5.0.0-SNAPSHOT
-$ ./bin/servicemix</code></pre></div><p>!/quickstart/images/start-linux.png</p>|width=75%|height=75%!
+                              <h1 id="Installation">Installation</h1><p>Before we can start working with Apache ServiceMix, we have to get it installed and running on our local machine first.</p><h2 id="Systemrequirements">System requirements</h2><p>For running Apache ServiceMix itself, you'll need</p><ul><li><p>Java Runtime Environment (JRE) 1.6.x (Java 6) or<br/>  Java Runtime Environment (JRE) 1.7.x (Java 7)</p></li><li><p>About 100 MB of free disk space for the default assembly</p></li></ul><p>If you're developing your own integration applications and OSGi bundles, you'll also need</p><ul><li><p>Java Developer Kit (JDK) 1.6.x (Java 6) or<br/>  Java Developer Kit (JDK) 1.7.x (Java 7)</p></li><li><p>Apache Maven 3.0.4 or higher</p></li></ul><h2 id="DownloadingApacheServiceMix">Downloading Apache ServiceMix</h2><p>Apache ServiceMix 5.0.0-SNAPSHOT is available under the Apache License v2 and can be downloaded from <a href="http://servicemix.apache.org/downloads.html">http://servicem
 ix.apache.org/downloads.html</a>.</p><p>Depending on your operation system, you should download either the tar.gz or the zip file:</p><ul><li><p><tt>tar.gz</tt> for Linux/Unix/MacOS X</p></li><li><p><tt>zip</tt> for Windows</p></li></ul><h2 id="InstallingApacheServiceMix">Installing Apache ServiceMix</h2><p>Installing Apache ServiceMix is as simple as uncompressing the downloaded archive on your hard disk.  For the rest of this guide, we'll refer to the this location as <strong><tt>&lt;SERVICEMIX_HOME></tt></strong>.</p><h2 id="StartingApacheServiceMix">Starting Apache ServiceMix</h2><p>Depending on your platform, start Apache ServiceMix by following the instructions below.  After starting the container, you will have access to the console from which you can manage the container.</p><h3 id="OnWindows">On Windows</h3><p>In a command prompt window, navigate to the directory where you extracted ServiceMix and run the <tt>bin\servicemix.bat</tt> file.</p><p>Example: if ServiceMix in ins
 talled in the <tt>c:\tools\apache-servicemix-5.0.0-SNAPSHOT</tt> directory</p><div class="syntax"><div class="highlight"><pre><span class="p">&gt;</span> <span class="n">cd</span> c:\tools\apache-servicemix<span class="m">-5</span>.<span class="m">0</span>.<span class="m">0</span>-SNAPSHOT&#x000A;&gt; .\bin\servicemix&#x000A;</pre></div>&#x000A;</div><p><img border="0" src="images/start-windows.png"/></p><h3 id="OnLinuxUnixMacOSX">On Linux/Unix/MacOS X</h3><p>On a command shell, navigate to the directory where you extracted ServiceMix and the <tt>bin/servicemix</tt> shell script</p><p>Example: if ServiceMix is installed in the <tt>~/Applications/apache-servicemix-5.0.0-SNAPSHOT</tt> directory.</p><div class="syntax"><div class="highlight"><pre><span class="nv">$ </span><span class="nb">cd</span> ~/Applications/apache-servicemix-5.0.0-SNAPSHOT&#x000A;<span class="nv">$ </span>./bin/servicemix&#x000A;</pre></div>&#x000A;</div><p>!/quickstart/images/start-linux.png</p>|width=75%|height
 =75%!
         </div>
       
           </div>
     <div id="siteFooter">
-      &copy; 2008-2012 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
+      &copy; 2008-2014 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
       <br/>
       Apache ServiceMix, ServiceMix, Apache, the Apache feather logo, and the Apache ServiceMix project logo are trademarks of The Apache Software Foundation.
     </div>



Mime
View raw message