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 2019/12/18 12:24:55 UTC

[GitHub] [camel-quarkus] ppalaga opened a new issue #159: Consider importing camel-bom in camel-quarkus-bom

ppalaga opened a new issue #159: Consider importing camel-bom in camel-quarkus-bom
URL: https://github.com/apache/camel-quarkus/issues/159
 
 
   Consider importing camel-bom in camel-quarkus-bom instead of managing the Camel components ourselves. 
   
   Pros:
   
   * This would make the life easier to us (camel-quarkus)
     * by having to maintain less lines of code in camel-quarkus-bom
     * by not having to add the camel libs when adding new extensions
   * This would make the live easier to our users when using components that do not have an extension yet.
   
   Cons: 
   
   * The Camel BOM contains some stuff that we and our users do not need, such as `*-starter` s. Not sure this could be harmful in any situation.
   
   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