[GitHub] [camel-quarkus] lburgazzoli opened a new issue #616: Utility to generate/scaffold an extension for a camel component

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-quarkus] lburgazzoli opened a new issue #616: Utility to generate/scaffold an extension for a camel component

GitBox
lburgazzoli opened a new issue #616: Utility to generate/scaffold an extension for a camel component
URL: https://github.com/apache/camel-quarkus/issues/616
 
 
   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

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
[hidden email]


With regards,
Apache Git Services
Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-quarkus] lburgazzoli commented on issue #616: Utility to generate/scaffold an extension for a camel component

GitBox
lburgazzoli commented on issue #616: Utility to generate/scaffold an extension for a camel component
URL: https://github.com/apache/camel-quarkus/issues/616#issuecomment-573579694
 
 
   Depends on https://issues.apache.org/jira/browse/CAMEL-14394

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
[hidden email]


With regards,
Apache Git Services
Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-quarkus] lburgazzoli commented on issue #616: Utility to generate/scaffold an extension for a camel component

GitBox
In reply to this post by GitBox
lburgazzoli commented on issue #616: Utility to generate/scaffold an extension for a camel component
URL: https://github.com/apache/camel-quarkus/issues/616#issuecomment-575550603
 
 
   Would be nice if such tool could automatically create the `quarkus-extension.yaml` taking info from the Apache Camel Catalog

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
[hidden email]


With regards,
Apache Git Services
Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-quarkus] lburgazzoli commented on issue #616: Utility to generate/scaffold an extension for a camel component

GitBox
In reply to this post by GitBox
lburgazzoli commented on issue #616: Utility to generate/scaffold an extension for a camel component
URL: https://github.com/apache/camel-quarkus/issues/616#issuecomment-597220477
 
 
   /cc @ppalaga

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
[hidden email]


With regards,
Apache Git Services
Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-quarkus] ppalaga commented on issue #616: Utility to generate/scaffold an extension for a camel component

GitBox
In reply to this post by GitBox
ppalaga commented on issue #616: Utility to generate/scaffold an extension for a camel component
URL: https://github.com/apache/camel-quarkus/issues/616#issuecomment-599395886
 
 
   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 Extensions
   
   As I said I'd prefer to have the JVM-only extensions in a separate directory.
   
   Current:
   
   ```
   .
   ├── ...
   ├── extensions
   ├── extensions-core
   ├── extensions-support
   └── ...
   ```
   
   Proposed:
   
   ```
   .
   ├── ...
   ├── extensions
   ├── extensions-core
   ├── extensions-support
   ├── extensions-JVM
   └── ...
   ```
   
   ## Itests of JVM-only Extensions
   
   I 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
   
   ```
   ├── ...
   ├── extensions-jvm
   │   ├── extension-1
   │   │   ├── deployment
   │   │   ├── runtime
   │   │   └── integration-test
   │   ├── extension-2
   │   │   ├── deployment
   │   │   ├── runtime
   │   │   └── integration-test
   │   ├── ...
   └── ...
   ```
   
   Pros/cons:
   
   * Easy to move the whole extension to the appropriate directory when promoting from the JVM-only state to the full support.
   * Wild idea: We should have isolated per extension tests for all new and existing extensions. The grouping of itests, that we currently do to reduce the CI times should be done by a tool that would merge several isolated itests into one. The isolated itests should be run by the CI regularly at least in the JVM mode to make sure that the dependencies are correct. The isolated itests should be run in the native mode on demand, e.g. before the release.
   
   WDYT?
   

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
[hidden email]


With regards,
Apache Git Services
Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-quarkus] lburgazzoli commented on issue #616: Utility to generate/scaffold an extension for a camel component

GitBox
In reply to this post by GitBox
lburgazzoli commented on issue #616: Utility to generate/scaffold an extension for a camel component
URL: https://github.com/apache/camel-quarkus/issues/616#issuecomment-599550561
 
 
   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

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
[hidden email]


With regards,
Apache Git Services
Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-quarkus] ppalaga commented on issue #616: Utility to generate/scaffold an extension for a camel component

GitBox
In reply to this post by GitBox
ppalaga commented on issue #616: Utility to generate/scaffold an extension for a camel component
URL: https://github.com/apache/camel-quarkus/issues/616#issuecomment-604052589
 
 
   `mvn cq:create -N -Dcq.artifactIdBase=foo` fulfills the named requirements, IMO. Can we close this @lburgazzoli ?

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
[hidden email]


With regards,
Apache Git Services
Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-quarkus] lburgazzoli closed issue #616: Utility to generate/scaffold an extension for a camel component

GitBox
In reply to this post by GitBox
lburgazzoli closed issue #616: Utility to generate/scaffold an extension for a camel component
URL: https://github.com/apache/camel-quarkus/issues/616
 
 
   

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
[hidden email]


With regards,
Apache Git Services