Hum, the problem is different from what I thought. The jaxb-api dependency is present in the dependencies. So it looks really weird. We had issues with some of the JAXB dependencies having invalid poms so maybe that's it. We upgraded JAXB for CR2, let's see if it fixes the issue. |