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 2019/03/14 08:18:00 UTC

[jira] [Commented] (CAMEL-13326) apt compiler - Separate core vs component processors

    [ https://issues.apache.org/jira/browse/CAMEL-13326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16792445#comment-16792445 ] 

Claus Ibsen commented on CAMEL-13326:
-------------------------------------

Ah we have apt as provided scope for camel-core which then have all the extra stuff that we dont need normally. But when you then have other components that has dependency on camel-core then we drag in the apt compiler plugin for camel-core.

So this requires maybe a splitup of the core modules once even more to come up with a nice way so users can depend on camel-core and not drag in a apt compiler that has the core only bits.

> apt compiler - Separate core vs component processors
> ----------------------------------------------------
>
>                 Key: CAMEL-13326
>                 URL: https://issues.apache.org/jira/browse/CAMEL-13326
>             Project: Camel
>          Issue Type: New Feature
>          Components: build system
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Major
>             Fix For: 3.0.0, 3.0.0-M2
>
>
> We should make camel-core / camel-spring / camel-blueprint have their own set of apt compiler plugins. And then another set for the general components etc.
> This avoids running some of these on modules they dont need to do.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)