The Manifest is not created in target/classes

[cschneider]

I am looking into using the content of target/classes to install bundles in exploded form to allow better debugging/change support.

The problem is that the bnd-maven-plugin does not seem to write the Manifest file into the target/classes dir. So it is not treated correctly.

This is also a problem when using bundles with felix connect. If the project is opened in the workspace then m2e links the project directly instead of using the jar. As the Manifest and possibly other artifacts are missing this does not work. So the only way to make sure my bundles start in felix connect is to close all projects hosting any bundles I use before starting the run.

[cschneider]

Seems this is not the problem. The Manifest is put into target/classes correctly. Not sure why felix connect does not pick it up. Will dig into the ClassPathScanner of connect.