I reverted my changes (even if I consider it's not a good idea ;)), but
I wonder what we can put in the documentation.
If, in the documentation, for instance, we say, "to be able to install
to deploy camel-hdfs in Karaf, you have the install xml-specs-api
feature first", the user will say: "wh
OK I revert my change, but I don't think it's good because:
1/ it works like this in 2.8
2/ it doesn't solve the runtime issue, and it introduces a new issue for
feature installation
Regards
JB
On 12/26/2011 04:23 AM, Willem Jiang wrote:
No, I don't think it's a good idea.
As you know we ca
That is why we should leave the javax api work to the OSGi container.
If we did a wrong assuming in the apache-camel feature, we will mass up
the whole container run time.
Why don't we let the container do its own business.
On 12/24/11 4:56 PM, Jean-Baptiste Onofré wrote:
FYI,
karaf@root> p
No, I don't think it's a good idea.
As you know we can not assume that user don't use a customized Karaf,
as we should not assume the Karaf version years ago.
That could make apache-camel feature be supported by different version
of Karaf.
And we should not let the apache-camel feature to chang
