Willem, I was actually thinking we would drop the Camel features descriptor from the ServiceMix 4 build and integrate the features descriptor built by the Camel project itself. Not sure if it can be dropped in as a replacement, we might need a bit of XSL-T magic to re-align some versions on dependencies, but I would start by using the plain descriptor and see how far that gets us. There's no point in maintaining the same descriptor in both projects, is there?
Regards, Gert Vanthienen ------------------------ Open Source SOA: http://fusesource.com Blog: http://gertvanthienen.blogspot.com/ 2009/9/18 Willem Jiang <[email protected]>: > Hi Gert, > > I tried to update the current Servicemix camel feature with my fix of > OpenJPA bundle[1]. > It requires the camel-jpa module to use the new JPA spec which is submitted > into servicemix spec repository. > I'm no luck with replacing the genronimo-JPA with the new JPA spec by > changing the files in smx4/trunk/features/camel/camel-features. > > Is there anything that I'm missing ? > > [1] https://issues.apache.org/activemq/browse/SM-1876 > > Willem > >
