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.
There are several ways to import the projects into Eclipse.
At this point, usage of the m2e plugins to import Camel into Eclipse does not work due to plugins without LifeCycle hints, bundle plugin configuration problems, etc... Patches, notes, etc... to help get this supported would be more than welcome.
The maven-eclipse-plugin can be used to generate the .classpath/.project/.settings file that Eclipse need. To do this, run:
The latter is recommended as it would completely setup the workspace for you as well as provide options to wire in other projects also found in your workspace.
After running the above command, from within Eclipse, do "File -> Import -> Existing Projects into Workspace", select the root camel checkout location and Eclipse should find all the projects.
The above mentioned setup.eclipse profile does a few additional things to your workspace:
You can add a profile to your .m2/settings.xml to specify your eclipse workspace location so you can avoid having to type that each time you need to update the projects.
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.11.0 onwards, if you want Camel to be build against Spring 3.0 you have to build with the maven profile spring3.0.
From Camel 2.10.0 onwards, if you want Camel to be build against Spring 3.1 you have to build with the maven profile spring3.1.
From Camel 2.11.0 onwards, Spring 3.1 is the default.
Note: the camel-test-spring component requires to be built with Spring 3.1.
From Camel 2.11.0 onwards, if you want Camel to be build against Spring 3.2 you have to build with the maven profile spring3.2.
From Camel 2.12.0 onwards, Spring 3.2 is the default.
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.