You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by GitBox <gi...@apache.org> on 2020/03/10 13:30:47 UTC

[GitHub] [camel-quarkus] ppalaga opened a new issue #865: Re-org the source tree

ppalaga opened a new issue #865: Re-org the source tree
URL: https://github.com/apache/camel-quarkus/issues/865
 
 
   ## Goals
   
   * Reduce the number of extensions under `extensions`
   * Increase the visibility of the extensions now under `extensions/support`. They are hard to find for newcomers and they are hard to scroll to for maintainers
   
   ## Non-goals (possible future goals)
   
   * Split the extensions under `extensions` into even smaller groups, like we have in the GH workflow
   * Do anything with the itests
   
   ## Current state:
   
   ```
   ├── catalog
   ├── docs
   ├── examples
   ├── extensions
   │   ├── ...
   │   ├── support
   ├── integration-tests
   ├── poms
   └── tooling
   ```
   
   ## Proposed state
   
   ```
   ├── catalog
   ├── docs
   ├── examples
   ├── extensions
   ├── extensions-core       # The extensions whose camel artifacts are under core in the Camel source tree
   ├── extensions-support   # Moved from extensions/support
   ├── integration-tests
   ├── poms
   └── tooling
   
   ```
   
   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:
users@infra.apache.org


With regards,
Apache Git Services

[GitHub] [camel-quarkus] ppalaga commented on issue #865: Re-org the source tree

Posted by GitBox <gi...@apache.org>.
ppalaga commented on issue #865: Re-org the source tree
URL: https://github.com/apache/camel-quarkus/issues/865#issuecomment-597311265
 
 
   > > Fine with me, wonder if it could make sense to use `core` instead if `extensions-core` (same for `support`)
   > 
   > No problem, if you like it that way.
   
   Actually, we already have a module called `camel-quarkus-core` and I'd like to keep the naming scheme `artifactId = "camel-quarkus-" + dirName`. So `extensions-core` or `core-extensions` seems to be a better choice.

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services

[GitHub] [camel-quarkus] ppalaga commented on issue #865: Re-org the source tree

Posted by GitBox <gi...@apache.org>.
ppalaga commented on issue #865: Re-org the source tree
URL: https://github.com/apache/camel-quarkus/issues/865#issuecomment-597306205
 
 
   > Fine with me, wonder if it could make sense to use `core` instead if `extensions-core` (same for `support`)
   
   No problem, if you like it that way.
   
   Now pondering whether it is worth to have a common parent folder for the three extension folders. We currently have some sanity checks defined in `extensions` - I'd either have to move the def to the top pom or have them three times.

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services

[GitHub] [camel-quarkus] ppalaga closed issue #865: Re-org the source tree

Posted by GitBox <gi...@apache.org>.
ppalaga closed issue #865: Re-org the source tree
URL: https://github.com/apache/camel-quarkus/issues/865
 
 
   

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services

[GitHub] [camel-quarkus] lburgazzoli commented on issue #865: Re-org the source tree

Posted by GitBox <gi...@apache.org>.
lburgazzoli commented on issue #865: Re-org the source tree
URL: https://github.com/apache/camel-quarkus/issues/865#issuecomment-597219100
 
 
   Fine with me, wonder if it could make sense to use `core` instead if `extensions-core` (same for `support`)

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services

[GitHub] [camel-quarkus] ppalaga commented on issue #865: Re-org the source tree

Posted by GitBox <gi...@apache.org>.
ppalaga commented on issue #865: Re-org the source tree
URL: https://github.com/apache/camel-quarkus/issues/865#issuecomment-597306903
 
 
   I think I slightly prefer the option without the common parent folder for the three extension folders. It's less clicking around in the IDE. 

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services