dockerfor the native mode, see Building a native executable section of the Quarkus documentation.
Maven 3.5.3+ (unless you use the Maven Wrapper, a.k.a.
mvnwavailable in the source tree).
Checkout the code
git clone https://github.com/apache/camel-quarkus.git cd camel-quarkus
A fast build without tests:
mvn clean install -DskipTests
A build with integration tests in the JVM mode only:
mvn clean install
A build with integration tests in both the JVM mode and the native mode:
mvn clean install -Dnative
You should know how to build.
Go through the Quarkus extension author’s guide to get an idea what is expecting you.
Make sure that nobody else works on the same extension already by searching through the GitHub issues.
Let others know that you work on the given extension by either creating a new issue or asking to assign an existing one to you.
Scaffold the necessary Maven modules using
quarkus-maven-plugin. As an example let’s add a new extension for supporting an imaginary Camel component
cd camel-quarkus cd extensions mvn quarkus:create-extension groovy:execute@scaffold-integration-test -N \ -Dquarkus.artifactIdBase=foo \ -Dquarkus.nameBase="Foo"
foois the unique part of the new extension’s
Foois the unique part of the artifact name without the `Camel Quarkus :: ` prefix
nameprefixes and suffixes are added automatically by the plugin.
The above sequence of commands does the following:
It creates three new Maven modules under the
camel-quarkus-foo(a.k.a. the runtime module) and
These three modules are linked where necessary:
camel-quarkus-foo-parentis added to the
camel-quarkus-foois added to the
<dependencyManagement>of the runtime BOM (Bill of Materials)
camel-quarkus-foo-deploymentis added to the
<dependencyManagement>of the deployment BOM (Bill of Materials)
It creates a basic
FooProcessorclass in the deployment module.
It also creates a stub of an integration test module under
A compilation performed immediately after generating the modules should pass flawlessly but running the tests will fail because the test project needs to get finished.
nameBaseparameter of the mojo is optional. If you do not specify it on the command line, the plugin will derive it from
artifactIdBaseby replacing dashes with spaces and uppercasing each token. So you may consider omitting explicit
nameBasein some cases.
Complete the extension by adding dependencies to the runtime module. You probably want to add a dependency on on the given Camel component - in our case
Complete the integration test module under
integration-tests/foo. Make sure you test both the consumer and the producer of the component (if the component supports both). Make sure the tests are passing both in the JVM mode (
mvn test) and in the native mode (
mvn verify -Dnative).