To build camel maven has to be configured to use more memory
Available as of Camel 2.6
The following skips building the manual, the distro and does not execute the unit tests.
If you prefer to use an IDE then you can auto-generate the IDE's project files using maven plugins. e.g.
You can also find some helpful notes on usage here.
If you have not already done so, you will need to make Eclipse aware of the Maven repository so that it can build everything. In the preferences, go to Java->Build Path->Classpath and define a new Classpath Variable named M2_REPO that points to your local Maven repository (i.e., ~/.m2/repository on Unix and c:\Documents and Settings\<user>\.m2\repository on Windows).
You can also get Maven to do this for you:
To enable source style checking with checkstyle, build Camel with the -Psourcecheck parameter
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:
From Camel 2.4.0, we switch the default Spring version to 3.0.x, If you want Camel to be build against Spring 2.5.6 you have to build with the maven profile spring-2.x.
You may want to skip testing and do a fast build
Note: Spring 2.x is no longer supported from Camel 2.7 onwards. The spring-2.x profile has been removed.
If you change anything in the features.xml from platform/karaf 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 platform directory.