Author: buildbot
Date: Thu Apr 12 15:18:43 2012
New Revision: 812553
Log:
Production update by buildbot for camel
Modified:
websites/production/camel/content/cache/main.pageCache
websites/production/camel/content/camel-run-maven-goal.html
Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/camel/content/camel-run-maven-goal.html
==============================================================================
--- websites/production/camel/content/camel-run-maven-goal.html (original)
+++ websites/production/camel/content/camel-run-maven-goal.html Thu Apr 12 15:18:43 2012
@@ -96,7 +96,14 @@ META-INF/spring/*.xml
</pre>
</div></div>
-<p>This allows you to boot up any Spring services you wish; whether they are Camel
related or any other Spring POJOs.</p>
+<p>From <b>Camel 2.10</b> onwards the <tt>camel:run</tt> plugin
also supports running <a shape="rect" href="using-osgi-blueprint-with-camel.html" title="Using
OSGi blueprint with Camel">Blueprint</a> application, and by default it scans for
OSGi blueprint files in</p>
+<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
+<pre class="code-java">
+OSGI-INF/blueprint/*.xml
+</pre>
+</div></div>
+
+<p>This allows you to boot up any Spring services you wish; whether they are Camel
related or any other Spring POJOs or Blueprint.</p>
<p>If you want to boot up your Camel routes a little faster, you could try the <a
shape="rect" href="camel-embedded-maven-goal.html" title="Camel Embedded Maven Goal">camel:embedded</a>
instead.</p>
@@ -106,14 +113,30 @@ This feature could in some rare cases ca
<p>To enable it you should configure the <b>useDot</b> parameter:</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
-<pre class="code-java">
- <plugin>
- <groupId>org.apache.camel</groupId>
- <artifactId>camel-maven-plugin</artifactId>
- <configuration>
- <useDot><span class="code-keyword">true</span></useDot>
- </configuration>
- </plugin>
+<pre class="code-xml">
+ <span class="code-tag"><plugin></span>
+ <span class="code-tag"><groupId></span>org.apache.camel<span
class="code-tag"></groupId></span>
+ <span class="code-tag"><artifactId></span>camel-maven-plugin<span
class="code-tag"></artifactId></span>
+ <span class="code-tag"><configuration></span>
+ <span class="code-tag"><useDot></span>true<span class="code-tag"></useDot></span>
+ <span class="code-tag"></configuration></span>
+ <span class="code-tag"></plugin></span>
+</pre>
+</div></div>
+
+<h3><a shape="rect" name="CamelRunMavenGoal-Loggingclasspathbeingused"></a>Logging
classpath being used</h3>
+<p>From <b>Camel 2.10</b> onwards you can configure whether the classpath
should be logged when <tt>camel:run</tt> runs. In older releases the classpath
is always logged.<br clear="none">
+This can be verbose and noisy, so from Camel 2.10 onwards, the classpath is not logged anymore.
You can enable this in the configuration using:</p>
+
+<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
+<pre class="code-xml">
+ <span class="code-tag"><plugin></span>
+ <span class="code-tag"><groupId></span>org.apache.camel<span
class="code-tag"></groupId></span>
+ <span class="code-tag"><artifactId></span>camel-maven-plugin<span
class="code-tag"></artifactId></span>
+ <span class="code-tag"><configuration></span>
+ <span class="code-tag"><logClasspath></span>true<span
class="code-tag"></logClasspath></span>
+ <span class="code-tag"></configuration></span>
+ <span class="code-tag"></plugin></span>
</pre>
</div></div></div>
</td>
|