THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- Download and install Maven
(Maven 3.1.1 or newer is required to build Camel 2.14 onwards)
(Maven 3.2.5 or newer is required to build Camel 2.18 onwards) - Get the latest Source
- Java
(1.7 or 1.8 to build Camel 2.14 onwards)
(1.8 to build Camel 2.18 onwards)
Optional:
- Prince should be in the executable PATH to generate the PDF documentation
...
| Code Block | ||
|---|---|---|
| ||
mvn clean source:jar install -Pfastinstall
|
Building with Spring 3.0
...
Support for Spring 3.0 is deprecated from Camel 2.11 onwards.
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
|
Building with Spring 3.1
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, Spring 3.1 is the default.
Note: the camel-test-spring component requires to be built with Spring 3.1.
Building with Spring 3.2
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.13.0 onwards, if you want Camel to be build against Spring 4.0 to work around the back compatible issue CAMEL-7074, you have to build with the maven profile spring4.
| Code Block | ||
|---|---|---|
| ||
mvn clean install -Pspring4
|
From Camel 2.12.0 onwards, Spring 3.2 is the default.
...
Working with karaf features
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.
...