Hi Gert,
I think we can leverage the spring osgi bundle repository, so we don't
need to maintain the bundles ourself.
I'm +1 to add the the repo in the features.xml, like the mvn pom does :)
Willem
Gert Vanthienen wrote:
L.S.,
I'm writing a features.xml validator plugin and testing it on the
Apache Camel features.xml file. It shows that the camel-castor
feature is using a SpringSource bundle for castor. This means the
camel-castor feature can not be installed on Karaf without adding the
SpringSource bundle repository location to the configuration first.
Now, the question is how we are going to deal with this. As far as I
see, there are 3 options available:
- we can improve Karaf so it allows adding the repo to the
configuration from the features.xml file, so the springsource repo is
available when adding the features.xml file
- we can build a ServiceMix bundle for castor and release that into
central repo before we do the next release of Camel
- we can just document the fact that the repository url needs to be
added before using the Apache Camel features
What option do people prefer? Does anyone see another way of solving this?
Regards,
Gert Vanthienen
------------------------
Open Source SOA: http://fusesource.com
Blog: http://gertvanthienen.blogspot.com/
