[
https://issues.apache.org/jira/browse/CAMEL-3747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13028281#comment-13028281
]
Hadrian Zbarcea commented on CAMEL-3747:
----------------------------------------
@Ashwin, no you are correct, that would be the drawback. We still have too many
archetypes that could be consolidated. For instance the activemq one could be
consolidated with the java and spring ones with comments about how to
enable/disable functionality. Even the java and spring could be one archetype.
I'll have to think about a good way to do that. I don't know if there would be
a solution to make everybody happy. Partial archetypes would be an option too.
Oh, well...
> create a camel bundle archetype
> -------------------------------
>
> Key: CAMEL-3747
> URL: https://issues.apache.org/jira/browse/CAMEL-3747
> Project: Camel
> Issue Type: New Feature
> Components: tooling
> Reporter: james strachan
> Assignee: Ashwin Karpe
> Fix For: 2.8.0
>
>
> we don't have an archetype yet for creating a camel route as an OSGi bundle.
> Might be worth creating one so folks hacking camel can easily make a jar +
> bundle in the same archetype.
> Maybe a Spring one and a blueprint one?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
