Hi

Do you use jaxb version provided by the plugin ou you define your own jaxb 
version ?

Regards 
JB

> Le 27 nov. 2021 à 20:22, Bernd Eckenfels <e...@zusammenkunft.net> a écrit :
> 
> Hello Steven
> 
> How do the child elements of that element look like? Are they using 
> default/f/ns2 prefix and maybe the (semantically equivalent) change affects 
> your memory only because the old form ignored a actual entry for dependency?
> 
> Bernd
> 
> --
> http://bernd.eckenfels.net
> ________________________________
> Von: Romain Manni-Bucau <rmannibu...@gmail.com>
> Gesendet: Samstag, November 27, 2021 8:14 PM
> An: dev
> Betreff: Re: karaf-maven-plugin generates another 
> org.apache.karaf.features.xml with Java 8/Java 11
> 
> Hi Steven,
> 
> 
> Maybe force jaxb version to an earlier one in karag pluhin dependencies in
> your pom.
> 
> 
>> Le sam. 27 nov. 2021 à 20:05, Steven Huypens <steven.huyp...@gmail.com> a
>> écrit :
>> 
>> Hi all,
>> 
>> I tried to create my custom Karaf distribution (using karaf-maven-plugin
>> 4.3.2) with Java 11 for the first time, and I noticed a difference in the
>> resulting org.apache.karaf.features.xml
>> 
>> The line
>> 
>> <featuresProcessing xmlns="
>> http://karaf.apache.org/xmlns/features-processing/v1.0.0"; xmlns:f="
>> http://karaf.apache.org/xmlns/features/v1.6.0";>
>> 
>> has been changed into
>> 
>> <ns3:featuresProcessing xmlns:ns2="
>> http://karaf.apache.org/xmlns/features/v1.6.0"; xmlns:ns3="
>> http://karaf.apache.org/xmlns/features-processing/v1.0.0";>
>> 
>> which means a namespace has been added. Unfortunately this little change
>> has a big impact because now my app immediately runs OutOfMemory when I
>> start Karaf. There is very little DEBUG-logging, the behaviour is somewhat
>> like described in https://issues.apache.org/jira/browse/KARAF-6068
>> 
>> Removing the namespace fixes the problem.
>> 
>> 
>> 
>> Do you have any idea how I can prevent my app from going OOM after this
>> change ? Or how I can prevent the namespace from being added with Java 11 ?
>> It would be nice to understand the exact problem here.
>> 
>> 
>> 
>> Kind regards,
>> Steven
>> 

Reply via email to