Hi Ralf,
I would not specify flags by default.
You are right about the documentation of these flags. I updated it on
the "new" dev guide (that I will propose soon with the "new" website).
Regards
JB
On 11/22/2015 04:36 PM, rsteppac wrote:
Hi JB,
jbonofre wrote
It sounds like camel-jaxb is not install.
That's definitely the effect I observe the most. Though I don't think it is
the root cause. I see other issues as well. (NPE in
BundleRevisionImpl.getResourceLocal(..) and failed (re-)wiring to the SAAJ
implementation).
jbonofre wrote
Quick question: what do you use dependency and prerequisite flag in your
feature ?
Does it mean you have a custom distribution where you already have those
features installed by default (maybe boot features) ?
No, I have a plain vanilla Karaf to deploy into. Honestly, I am completely
ignorant about those two flags. They are not documented on the Karaf website
(or I have not searched thoroughly enough). My template feature.xml files do
not contain the flags, but they are generated (set to "false") by the
karaf-maven-plugin 4.0.x in the project that assembles the KAR artifact. So
I thought I try and see what observable effect they have. The behavior I
observed was that tagging every feature with prerequisite="true" increases
my chances of a successful deployment.
So you are saying that I should leave the properties at "false" if I am
deploying on a plain vanilla Karaf?
Thanks for your help!
Ralf
--
View this message in context:
http://karaf.922171.n3.nabble.com/KAR-deployment-in-Karaf-4-0-3-fails-with-varying-errors-tp4043649p4043656.html
Sent from the Karaf - User mailing list archive at Nabble.com.
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
