"Provided" Maven dependencies not included in p2 site

[knime]

If a Maven artifact has a "provided" dependency it won't be added to the p2 repository. This may lead to unresolved dependencies in an OSGi application because usually nothing is "provided" there (except some OSGi classes). Therefore I would also fetch and include provided dependencies in the p2 site.

[YoannBuch]

Hi knime, I think I ran into the same issue with a Spring artifact. Everything builds. But at runtime I get ClassNotFoundException on classes that are APIs (javax...). My guess it that their implementations did not make it to the class path maybe because they belong to an artifact marked as provided or optional.

Have you found a workaround? Thanks

[Vogel612]

The same problem applies to dependencies marked optional