[
https://issues.apache.org/jira/browse/CAMEL-9802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15230970#comment-15230970
]
David Gordon commented on CAMEL-9802:
-------------------------------------
I like this idea, because I think small, individually deployable examples not
only makes the examples easier to experiment with, but it also sort of fits in
with the spirit of microservices. I'm willing to help out with this, but I'd
like to bounce some thoughts around first before getting too far into
refactoring.
- Introducing the a BOM component to the individual example POMs eliminates
some concerns that are currently handled at the parent (or grandparent) POM
level, but just that change alone would not allow us to break away from the
hierarchy altogether, right?
- I'm interpreting the scope of this issue to be not only introducing the BOM
in the example POM, but also any additional refactoring that would eliminate
the need for POM inheritance altogether. Am I making the scope too big, or can
we generally agree on that interpretation?
- For any remaining configurations that are inherited from the parent or
grandparent, I think my approach would be to push them down into the individual
example POMs, essentially as-is. Am I oversimplifying?
- I believe this would end up resulting in a fair amount of repetitive XML
across example modules, but given the goals of this enhancement, is that an
acceptable thing?
> Camel examples - Make them standalone and import Camel BOM
> ----------------------------------------------------------
>
> Key: CAMEL-9802
> URL: https://issues.apache.org/jira/browse/CAMEL-9802
> Project: Camel
> Issue Type: Improvement
> Components: examples
> Reporter: Claus Ibsen
> Fix For: Future
>
>
> We should make the Camel examples not use a parent, but use Camel BOM
> instead, to make them standalone.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
