In reply to comment #19:
> I now have some other weird problems with package imports being visible in one
> bundle and not in another (while it is imported in the manifest even a require
> bundle on the offending bundle does not help) switching between project and
> maven artifact seems not to matter. Although another project appears twice in
> the bundle manifest container, I'll open another ticket for that issue (probably
> later today/tomorow have to switch to some other tasks for today).
Yes, please open a JIRA with some details to reproduce this.
> > Aside note: a new option appeared in the snapshot Preferences -> Spring
> ->Manifest Generation -> Scan output folders which is enabled by default. This
> pretty much makes the bundlor generated manifests useless, it misses a lot of
> packages. Often direct imports of classes (but this happens often yet
> inconsistently). To work around the lack of template.mf syntax for TEST.MF only
> imports we use some dummy java files that import something from the necessary
> packages, these get missed more often with this option turned on. (When it works
> it works perfectly though)
This is a new option which uses Bundlor default byte-code scanning on project output folders. As you are using a nightly build it could be that there are still issues with this new feature. If you experience issues please let me know with details on how to reproduce and I'll take a look.
There might be something special with your project setup that some classes or so are not being scanned. Right now I iterate over all output folders (project's default + output folder for each source folder) and scan that using default Bundlor byte-code scanning. Are you only using project source folders or do you use some kind of linking?