-
Notifications
You must be signed in to change notification settings - Fork 188
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Utility to generate/scaffold an extension for a camel component #616
Comments
Would be nice if such tool could automatically create the |
/cc @ppalaga |
I have the tool in a state where it is generating what I think is the right code. Now let's discuss the tree structure. JVM-only ExtensionsAs I said I'd prefer to have the JVM-only extensions in a separate directory. Current:
Proposed:
Itests of JVM-only ExtensionsI am not 100% sure what would be the best solution. I prefer having the itest as close as possible in the source tree to the corresponding extension to eliminate as much scrolling and clicking in the IDE. The most straightforward way to reach it would be
Pros/cons:
WDYT? |
No objection on my side, we can also think about moving individual extension integrations tests to the extension them-self and leave in the integration-tests folders only aggregate tests |
|
We should have an utility like https://github.com/apache/camel-spring-boot#creating--deleting-starters to generate/scaffold an extension out of a camel component
The text was updated successfully, but these errors were encountered: