You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2022/09/03 10:43:00 UTC

[jira] [Resolved] (CAMEL-17314) camel-dependencies - Filter to only include compile scoped dependencies

     [ https://issues.apache.org/jira/browse/CAMEL-17314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-17314.
---------------------------------
    Resolution: Won't Fix

> camel-dependencies - Filter to only include compile scoped dependencies
> -----------------------------------------------------------------------
>
>                 Key: CAMEL-17314
>                 URL: https://issues.apache.org/jira/browse/CAMEL-17314
>             Project: Camel
>          Issue Type: Improvement
>          Components: build system
>            Reporter: Claus Ibsen
>            Priority: Major
>             Fix For: 3.x
>
>
> camel-dependencies are used for aligning between Camel projects. However some end users may pickup the BOM to use the same versions as we used for building and testing Camel on that release.
> However we use some for testing, logging etc that are only for internal use.
> We can look at filtering the versions in the BOM to only include when they are compiled scoped - this should then leave out log4j, junit etc.
> This can then maybe help camel-dependencies be promoted to be more useable and supported for Camel end users.
> Otherwise Camel end users should favour using camel-bom which is the actual BOM - but this only has the Camel artifacts listed - not versions of 3rd party JARs.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)