Versions Compared

Key

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

...

1. Open an JIRA issue

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

2. Check the license of all dependencies

...

The source and resources have to follow some Apache/Camel coding rules:

  • Make sure every added source and resource contains the Apache license header.
  • Make sure the new component has an adequate test coverage.
  • Run a build with checkstyle to ensure the sources are conform with the Apache Camel coding rules: Building Camel (look for Building with checkstyle)
  • Make sure the log output is adequate on the INFO log level.

6. Check whether all dependencies are available as OSGI bundles

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

7. Add a new feature

...

Add the new component to the following files

  • parent/pom.xml
  • apache-camel/src/main/descriptors/common-bin.xml

Build the kit by running the following maven goal from the apache-camel directory:

...