...
To build camel maven has to be configured to use more memory
Unix/Linux/Mac
| Code Block |
|---|
|
export MAVEN_OPTS="-Xmx1024m -XX:MaxPermSize=512m"
|
Windows
| Code Block |
|---|
|
set MAVEN_OPTS=-Xmx1024m -XX:MaxPermSize=512m
|
A normal build
| Code Block |
|---|
|
mvn clean install
|
A normal build without running tests
| Code Block |
|---|
|
mvn clean install -Pfastinstall
|
A normal build without running tests but checkstyle verification enabled
| Code Block |
|---|
|
mvn clean install -Pfastinstall,sourcecheck
|
...
The following skips building the manual, the distro and does not execute the unit tests.
| Code Block |
|---|
|
mvn install -Pfastinstall
|
...
If you prefer to use an IDE then you can auto-generate the IDE's project files using maven plugins. e.g.
IntelliJ
Eclipse
There are several ways to import the projects into Eclipse.
...
The maven-eclipse-plugin can be used to generate the .classpath/.project/.settings file that Eclipse need. To do this, run:
| Code Block |
|---|
|
mvn process-test-sources eclipse:eclipse
|
| Tip |
|---|
| title | Enable the apt Profile explicitly if using Java 6 |
|---|
|
Per default this profile is enabled only when using Java 7+ however for many of the Camel components you would still need the org.apache.camel:spi-annotations Maven module on the class path inside the generated .classpath. To force this on Java 6 do: | Code Block |
|---|
|
mvn -Papt process-test-sources eclipse:eclipse
|
As otherwise some of the Camel components inside your eclipse workspace would not compile (when using Java 6) because the org.apache.camel:spi-annotations Maven module would be missing on the class path. |
or
| Code Block |
|---|
|
mvn -Psetup.eclipse -Declipse.workspace.dir=/path/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.
| Code Block |
|---|
|
<profiles>
<profile>
<id>setup.eclipse</id>
<properties>
<eclipse.workspace>/path/to/your/workspace</eclipse.workspace>
</properties>
</profile>
</profiles>
|
...
To enable source style checking with checkstyle, build Camel with the -Psourcecheck parameter
| Code Block |
|---|
|
mvn -Psourcecheck clean install
|
...
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:
| Code Block |
|---|
|
mvn clean source:jar install -Pfastinstall
|
...
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.
| Code Block |
|---|
|
mvn clean install -Pspring3.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.
| Code Block |
|---|
|
mvn clean install -Pspring3.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.
| Code Block |
|---|
|
mvn clean install -Pspring3.2
|
From Camel 2.12.0 onwards, Spring 3.2 is the default.
Building with Spring 4.0
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.
| Code Block |
|---|
|
mvn clean install -Pspring4
|
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.
| Code Block |
|---|
|
mvn clean install -Pvalidate
|
...
