Embedding dependencies such as Xerces may be a bit difficult, depending on how you use it. For example if you use the standard xml api, the api will most certainly use the parser from the JVM. In order to use your own copy of xerces, you need to create your factories explicitly i think.
On a more general note, one thing that might be doable, would be to "generate" the packages.extra or boot delegation package list at startup time. We do that offline during the build of the assembly based on the jars included in the lib folder, but we could add an option to do that during startup. A slightly different way would be to better support the notion of library when installing features, and not only while building assemblies. Those libraries are used to add such providers (xerces, xalan, etc...) to the endorsed folders, but you can't really add them at runtime. 2016-08-26 6:52 GMT+02:00 thully <[email protected]>: > Our users are just using maven-bundle-plugin. Whenever they've tried > depending directly on projects that depend Xerces and use > Embed-Dependencies > as they would for any other dependency they want to embed, the resulting > bundle does not load properly. What do they need to do differently due to > Xerces being included in the Karaf distribution? > > > > -- > View this message in context: http://karaf.922171.n3.nabble. > com/Application-using-Karaf-problems-with-packages-not- > being-exported-by-default-configuration-tp4047592p4047690.html > Sent from the Karaf - User mailing list archive at Nabble.com. > -- ------------------------ Guillaume Nodet ------------------------ Red Hat, Open Source Integration Email: [email protected] Web: http://fusesource.com Blog: http://gnodet.blogspot.com/
