A Maven runtime profile configures how Maven invokes Apache Camel. A Maven runtime profile stores the Maven goals to execute, any Maven profiles to use, the version of Maven to use, the JRE to use, the classpath to use, any environment variables that need to be set, and a few other pieces of information.
The runtime configuration editor for a Fuse IDE runtime profile contains the following tabs:
Main—specifies the Maven goals, the Maven profiles, any Maven properties that need to be set and the version of Maven to use.
JRE—specifies the JRE to use.
Refresh—specifies how Maven refreshes the project's resource files when it completes.
Environment—specifies any environment variables that need to be set.
Common—specifies how Eclipse stores the profile and displays the output.
The first time a Apache Camel route is run using Maven, you create a default runtime profile that should not require editing.
The most commonly used goal when running a route is camel:run
. It
loads the routes into a Spring container running in its own JVM.
The Apache Camel plug-in also supports a camel:embedded
goal that loads the
Spring container into the same JVM as the used by Maven. The advantage of this is that
the routes should bootstrap faster.
If your POM contains other goals, you can change the Maven goal used by editing the Goals field on the Main tab.
By default, the m2Eclipse plug-in uses its embedded version of Maven. If you want to use a specific version of Maven or have a newer version installed on your development machine, you can change the version by editing the Maven Runtime field on the Main tab.
![]() | Important |
---|---|
Apache Camel requires Maven 3. |
By default, the output from the route execution is sent to an Eclipse Console view. It can, however, be redirected to a file if needed.
To redirect the output to a file:
Select the Common tab.
Check the box next to the File: field.
Enter the path to the file where the output will be redirected.
The
, , and buttons can help you build the path to the output file.