Hi James, You are right, we need two separate archetypes, one for spring and one for blueprint.
Remark : the ServiceMix projects already has a archetype for camel-osgi-spring --> http://repo.fusesource.com/nexus/content/repositories/releases/org/apache/servicemix/tooling/servicemix-camel-osgi-bundle/2011.01.0-fuse-00-00/ Regards, Charles On Thu, Mar 3, 2011 at 10:59 AM, james strachan (JIRA) <j...@apache.org> wrote: > create a camel bundle archetype > ------------------------------- > > Key: CAMEL-3747 > URL: https://issues.apache.org/jira/browse/CAMEL-3747 > Project: Camel > Issue Type: Improvement > Reporter: james strachan > Fix For: 2.7.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 > > >
