You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@camel.apache.org by "Luca Burgazzoli (Jira)" <ji...@apache.org> on 2020/01/06 17:06:00 UTC

[jira] [Updated] (CAMEL-14367) review netty-all usage

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

Luca Burgazzoli updated CAMEL-14367:
------------------------------------
    Description: 
Some components, such as camel-netty or camel-ahc have a dependency on netty-all, this is usually fine but I think we should review this policy as:
- it will make the dependencies list even more modular and minimal
- it will play better wit camel-quarkus as netty-all may bring some unwanted classes that may cause troubles to the native compilation 

  was:
Some components, such as camel-netty or camel-ahc have a dependency on netty-all, this is usually fine but I think we should review this policy as:
- it will make the dependencies list even more modular ar minimal
- it will play better wit camel-quarkus as netty-all may bring some unwanted classes that may cause troubles to the native compilation 


> review netty-all usage
> ----------------------
>
>                 Key: CAMEL-14367
>                 URL: https://issues.apache.org/jira/browse/CAMEL-14367
>             Project: Camel
>          Issue Type: Improvement
>            Reporter: Luca Burgazzoli
>            Priority: Minor
>
> Some components, such as camel-netty or camel-ahc have a dependency on netty-all, this is usually fine but I think we should review this policy as:
> - it will make the dependencies list even more modular and minimal
> - it will play better wit camel-quarkus as netty-all may bring some unwanted classes that may cause troubles to the native compilation 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)