FYI,
I submitted a patch for that in CAMEL-3995.
Regards
JB
On 05/19/2011 03:59 PM, Willem Jiang wrote:
+1 for this suggestion.
I think we could add a option to let the karaf feature validate plugin
to load the features that karaf has before starting the validation.
On 5/19/11 8:16 PM, Jean-Baptiste Onofré wrote:
Hi guys,
from a general point of view, I prefer to not define Karaf in the
feature <repositories/> set.
The Karaf features are available by default in the Karaf runtime.
So simply adding:
<feature ...>
<feature>war</feature>
</feature>
will install the war feature provided by Karaf.
Pros:
- you aren't link to a Karaf version
Cons:
- the features plugin validate goal won't work as it doesn't know the
Karaf features without the repositories definition
Anyway, for now, I think it's better to not define karaf features
descriptor in the <repositories/> section.
Regards
JB
On 05/19/2011 01:46 PM, Willem Jiang wrote:
Hi,
As apache-camel feature is using the karaf features, such as Jetty and
Spring. These features need a certain version of Karaf, so we specify
the repository in the camel feature file.
On 5/19/11 7:43 PM, James Talbut wrote:
Hi,
The Camel standard features file contains:
<repository>mvn:org.apache.karaf.assemblies.features/standard/2.2.0/xml/features</repository>
Is this beneficial, as it ties the version of Camel in to a specific
version of karaf?
Without that line the user will be required to specify the karaf url
themselves, but that's the default for karaf anyway.
Jim
