Automate the process of creating jvm only extensions #1974
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
oscerd
approved these changes
Oct 30, 2020
ppalaga
approved these changes
Oct 30, 2020
jamesnetherton
force-pushed
the
auto-jvm-extensions
branch
from
be9505d
to
5215d63
Compare
|
Latest commit updates the input parameter description. I'll merge and try it out on |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a bit of an experiment which we can always remove if it ends up being not useful.
It lets you create JVM only extensions for a list of camel components. To run you'd do:
Actions -> Generate JVM Extensions -> Run Workflow
Then enter a list of artifact ids to add. It'll run the cq-maven-plugin, make sure the tests pass & create a PR.