Hello.
Has anyone else observed optional package resolution issues on karaf 4.4.1-SNAPSHOT. When I build the karaf deployment for my application the majority of the base artifacts get added to the etc/startup.cfg file. These in turn get loaded by the main deployment thread in karaf. At the end of the deployment process these bundles get re-assessed to see if the bundles need to get updated, however this process appears to ignore optional package requirements. The result is that many of the core services (such as spring-webmvc) fail to functional correctly. This wasn't an issue in karaf 4.3. As such, please can the community let me know if this is a general issue that has been seen elsewhere? Or is it something that is peculiar to my setup. Thanks Paul
