...
Code Block |
---|
META-INF/spring/*.xml |
From Camel 2.10 onwards the camel:run
plugin also supports running Blueprint application, and by default it scans for OSGi blueprint files in
Code Block |
---|
OSGI-INF/blueprint/*.xml
|
This allows you to boot up any Spring services you wish; whether they are Camel related or any other Spring POJOs or Blueprint.
If you want to boot up your Camel routes a little faster, you could try the camel:embedded instead.
...
To enable it you should configure the useDot parameter:
Code Block | ||||
---|---|---|---|---|
| ||||
<plugin>
<groupId>org.apache.camel</groupId>
<artifactId>camel-maven-plugin</artifactId>
<configuration>
<useDot>true</useDot>
</configuration>
</plugin>
|
Logging classpath being used
From Camel 2.10 onwards you can configure whether the classpath should be logged when camel:run
runs. In older releases the classpath is always logged.
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:
Code Block | ||||
---|---|---|---|---|
| ||||
<plugin>
<groupId>org.apache.camel</groupId>
<artifactId>camel-maven-plugin</artifactId>
<configuration>
<logClasspath>true</logClasspath>
</configuration>
</plugin>
|