Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

...

1. Open an JIRA issue

Open an JIRA issue at https://issues.apache.org/jira/browse/CAMELImage Removed, if its it does not already exist.
The issue type should be a "Task". A sample can be found here: https://issues.apache.org/jira/browse/CAMEL-3471Image Removed

2. Change the parent pom

All dependency versions are managed in the parent pom. Change the version number for the dependency you want to upgrade in this file.

3. Customize the source code (if

...

necessary)

If this upgrade is a major change (e.g. from Apache Mina 1.1.7 to 2.0.2), it could require some source code and/or test customizations. Be careful with changes in the unit tests!

4. Ask for an OSGI-fied version (if

...

necessary)

If this dependency is not provided available as an OSGI bundle, ask the Apache Servicemix guys for an OSGI-fied version of this dependency. You should do this by open an opening a JIRA issue at https://issues.apache.org/jira/browse/SMX4Image Removed
The issue type should be a "Task". A sample can be found here: https://issues.apache.org/jira/browse/SMX4-699Image Removed

5. Change the platform/karaf pom (if

...

necessary)

If a new OSGI-fied version of this dependency is provided, update the platform/karaf pom with the new version.

6. Validate the features.xml (if

...

necessary)

If you change anything in the features.xml from platform/karaf you can should run a validation step test to ensure the generated features.xml file is correct. You can do this running the following maven goal from the platform directory.

...