Yeah, maybe the properties in etc/config.properties should include an additional property that would be taken from etc/custom.properties so that it would be much easier to add stuff. Please raise a JIRA if you think that would suit your needs.
2016-08-31 0:48 GMT+02:00 thully <tmh...@eng.ucsd.edu>: > I figured out why that was happening - it turns out we had packages listed > in > org.osgi.framework.system.packages.extra in custom.properties that were > overriding the defaults in config.properties. As such, Xerces was never > being exported, and org.apache.xerces.util isn't in boot delegation so we > can't get access to it that way. Once I moved the custom additions to > org.osgi.framework.system.packages.extra from custom.properties to > config.properties, the bundle worked. > > With that said, what would be the best practice as far as adding system > packages to a custom Karaf distribution and preserving the defaults? It > seems someone added these to our custom.properties a long time ago, and I > suspect they didn't realize it would prevent the defaults from being > exported (we can into the same issue with sun.* packages and bootdelegation > a while back). > > > > -- > View this message in context: http://karaf.922171.n3.nabble. > com/Application-using-Karaf-problems-with-packages-not- > being-exported-by-default-configuration-tp4047592p4047767.html > Sent from the Karaf - User mailing list archive at Nabble.com. > -- ------------------------ Guillaume Nodet ------------------------ Red Hat, Open Source Integration Email: gno...@redhat.com Web: http://fusesource.com Blog: http://gnodet.blogspot.com/
