[
https://issues.apache.org/jira/browse/CAMEL-4013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13190983#comment-13190983
]
Claus Ibsen commented on CAMEL-4013:
------------------------------------
Matt
It is a step in the right direction.
I wonder if we could improve this in a couple of ways
The minor stuff:
a) the snapshot repos is not needed for GA releases, so I would like the
pom.xml to be neat and cleaner
b) do we really need the apache license and organization referral? eg the
example is supposed to be templates people can copy and use
The serious stuff:
c) the OSGi plugin is overly complex as it is. People getting started with
Camel and OSGi will get scared like **** if they see all this XML stuff they
would have no clue why it is like that, and if they need to change something,
what should they touch.
For (c) we should need to remove stuff in the bundle plugin that is not needed.
eg if you look at today how the MANIFEST.MF is generated. We should try to hit
the same. I guess each example may need to be tailored to fit better. But
ideally it should just be a standard felix-bundle-plugin, with as few
configurations as possible. The example should ideally "just work" with OSGi.
> examples - Do not inherit pom.xml from parent to make it easy to copy example
> -----------------------------------------------------------------------------
>
> Key: CAMEL-4013
> URL: https://issues.apache.org/jira/browse/CAMEL-4013
> Project: Camel
> Issue Type: Improvement
> Components: examples
> Affects Versions: 2.7.0
> Reporter: Claus Ibsen
> Priority: Minor
> Fix For: Future
>
> Attachments: non_inherit_examples.patch
>
>
> We should not inherit any parent pom.xml files in any of the examples.
> Instead we should make the pom.xml file completely standalone. Then its
> easier for end users to copy the examples and customize those to their needs.
> For example to adjust camel version and whatnot.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
