christophd opened a new pull request, #15044: URL: https://github.com/apache/camel/pull/15044
# Description Kamelets are still kind of separated from the Camel core project. The Kamelets live in a separate GitHub project repository (https://github.com/apache/camel-kamelets) and follow a separate release lifecycle which creates cyclic module dependencies. In addition to that, writing and maintaining Kamelets is no fun as it boils down to writing YAML files manually. This PR shows a potential way to move Kamelets into the Camel core project. The Kamelets are written in Java instead of YAML and use of a new service provider annotation `@KameletSpec`. The Kamelets are discoverable via service loader discovery mechanism. The metadata as well as the service loader information is auto-generated by the Camel Maven plugin tooling. The Kamelets also become part of the Camel catalog. The PR implements a few Kamelets as an example: - set-body-action - data-type-action - timer-source - log-sink <!-- - Write a pull request description that is detailed enough to understand what the pull request does, how, and why. --> # Target - [x] I checked that the commit is targeting the correct branch (note that Camel 3 uses `camel-3.x`, whereas Camel 4 uses the `main` branch) # Tracking - [x] If this is a large change, bug fix, or code improvement, I checked there is a [JIRA issue](https://issues.apache.org/jira/browse/CAMEL) filed for the change (usually before you start working on it). See CAMEL-21049 <!-- # *Note*: trivial changes like, typos, minor documentation fixes and other small items do not require a JIRA issue. In this case your pull request should address just this issue, without pulling in other changes. --> # Apache Camel coding standards and style - [x] I checked that each commit in the pull request has a meaningful subject line and body. <!-- If you're unsure, you can format the pull request title like `[CAMEL-XXX] Fixes bug in camel-file component`, where you replace `CAMEL-XXX` with the appropriate JIRA issue. --> - [x] I have run `mvn clean install -DskipTests` locally and I have committed all auto-generated changes <!-- You can run the aforementioned command in your module so that the build auto-formats your code. This will also be verified as part of the checks and your PR may be rejected if if there are uncommited changes after running `mvn clean install -DskipTests`. You can learn more about the contribution guidelines at https://github.com/apache/camel/blob/main/CONTRIBUTING.md --> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
