Additional point about archetype. I propose that we create a new directory for the archetype which are specific for platform OSGI and of course for ServiceMix 4. This folder can contain the following archetypes :
- osgi-features = maven project + xml features file - osgi-camel-spring - osgi-camel-blueprint (when camel-blueprint will be ready) - osgi-pojo-spring - osgi-servicemix-project = parent pom containing list of modules to be installed in maven repo + dependencies definition + maven-bundle-plugin definition - osgi-config-spring = maven project + src/main/resources/META-INF/spring (could be used to place spring activemq.xml config file, ....) For JBI, clarification is requested as normally a JBI project is packaged as a collection of jar/zip in sa zip file + jbi/config.xml and thus is slighty different from OSGI bundles philosophy. Regards, Charles Moulliard Senior Enterprise Architect Apache Camel Committer ***************************** blog : http://cmoulliard.blogspot.com twitter : http://twitter.com/cmoulliard Linkedlin : http://www.linkedin.com/in/charlesmoulliard Apache Camel Group : http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm On Mon, Dec 7, 2009 at 8:48 AM, Jean-Baptiste Onofré <[email protected]>wrote: > Hi Gert, > > I think it's better to release archetpye 2009.01 before upgrading to > 2009.02. As the 2009.01 components have been released, it's logical to link > the archetype. Else, I'm afraid that the users are confused. > > Regards > JB > > Gert Vanthienen wrote: > >> L.S., >> >> I just realized the current version of the archetypes is still >> 2009.01-SNAPSHOT -- it looks like we never released the archetypes >> after our last 3.3.1 and 4.0.0 release. As soon as Camel 2.1 is out, >> we should be ready to go for components 2009.02 and I think it would >> make more sense to have a matching archetypes version of 2009.02 at >> that point as well. My main question is: should we just skip the >> archetypes version 2009.01 and release 2009.02 as soon as the >> components' release is out? Or should we go ahead now and release >> archetypes 2009.01 before we do the next release of components? >> >> I wouldn't mind doing the extra release if that's what we choose, but >> if we don't think it is a useful exercise at this time any more with >> the next version coming up soon, it might not be worth investing the >> time/effort. >> >> Regards, >> >> Gert Vanthienen >> ------------------------ >> Open Source SOA: http://fusesource.com >> Blog: http://gertvanthienen.blogspot.com/ >> >
