Currently, the maven-pax-plugin only adds provided and test dependencies to the Eclipse classpath.
This is done because Eclipse/PDE uses the manifest to determine the Plug-in Dependencies, so we
cannot assume these dependencies will be found by PDE even if they are plug-ins or OSGi bundles.
Therefore we add them as Required Libraries, so they will always be found.
Compile and runtime scope dependencies weren't previously added because it was assumed they
would be used when embedding content inside bundles - and embedded entries already appear on
the classpath, hence no need to add the raw dependencies.
However, people often add bundle dependencies with the default scope (compile) which means that
they wouldn't see these dependencies (as they might expect) - so to make things simpler I've decided
to add all Maven dependencies to the Eclipse classpath.
Improvement
Closed
Minor
Add all Maven compilation dependencies to the Eclipse classpath
"compile" - contains classes/resources that I want to embed
because my code needs them to load and I don't
expect them to be provided by another bundle.
"runtime" - contains classes/resources that I want to embed
because my code might need them during runtime
(via reflection, etc.) and I don't expect them to be
provided by another bundle
"provided" - contains classes/resources that I expect to be
provided by another bundle or the framework
"test" - contains classes/resources used in any unit or
integration tests (ie. not needed to load/run the
bundle - just needed to test with)