Good morning JB, with the karaf-maven-plugin? If so is it enough to add jaxb-api as dependency?
kind regards christian > Am 17.05.2019 um 05:54 schrieb Jean-Baptiste Onofré <j...@nanthrax.net>: > > Hi Christian, > > Maybe you can upgrade jaxb directly provided by Karaf ? > > Regards > JB > > On 16/05/2019 21:38, Christian Lutz wrote: >> Hello, >> >> I am using karat 4.1.7 (jdk8) on Windows 10 and I got in the situation where >> the bundle start fails because java.xml.bind can be found via two different >> paths. >> The first path is from my own deployed kar file. The other one is provided >> by the karat itself. >> >> The reason why I have added jaxb-api is one of my required bundles requires >> jaxb-api in version >=2.3.0 so I added this bundle to the kar file. >> If I execute bundle:refresh manually after the karat has been started on >> jaxb-api 2.3.1 bundle. I am able to start my own bundle. >> >> So my question is how can I enforce that the jaxb-api 2.3.1 bundle will be >> used and no manual bundle:refresh is necessary anymore. >> >> What I tried so far: >> - Removing javax.xml.bind from jre.properties and config.properties -> karat >> doesn’t even start anymore >> - set dependency=„true“ for jab-api within feature.xml (kar source) -> same >> problem >> - change start-level within feature.xml for jaxb-api within feature.xml -> >> same problem >> >> kind regards >> christian >> >> >> > > -- > Jean-Baptiste Onofré > jbono...@apache.org > http://blog.nanthrax.net > Talend - http://www.talend.com
