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 2022/03/26 00:54:10 UTC

[GitHub] [camel-quarkus] jamesnetherton edited a comment on issue #3302: Better control what we manage in our BOM

jamesnetherton edited a comment on issue #3302:
URL: https://github.com/apache/camel-quarkus/issues/3302#issuecomment-989648677


   In general I see a lot of the BOM imports as being quite problematic. Especially since the ones for the third party extensions import `quarkus-bom`.
   
   5. Currently we have this mix of `quarkus-bom` versions being resolved in the build:
   
   1.3.3.Final
   2.0.0.Final
   2.1.0.Final
   2.2.3.Final
   2.5.0.Final
   2.5.1.Final
   2.6.0.CR1
   
   The main issue is that if something is removed from `quarkus-bom`, it ends up being silently added back again by one of the older BOM versions. Thus giving the potential for messing up our dependency management.


-- 
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.

To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org