Ah ok. As far as this issue goes that shouldn't affect anything though, right?
The only downside I can see is the artifact (in this case jaxb-impl) will be packaged up in the repo wasting some space. The features file generated for the kar still seems to be used even when using compile scope for a kar dependency in a karaf-assembly. This would explain why my jaxb problem went away when I discovered the excludedArtifacts config option. -- View this message in context: http://karaf.922171.n3.nabble.com/Dependency-on-Camel-brings-in-a-jaxb-impl-that-causes-a-use-constraint-violation-tp4037029p4037048.html Sent from the Karaf - User mailing list archive at Nabble.com.
