It is either finding the mini bundles in repository/ext and getting confused between that one and the one in usr or the package version doesn't match. Can you double check the manifest in your mini bundle and the 'pshd.plan-3.2-ru.focusmedia.odp.poim.server' bundle.

This only works if the plan is scoped. Did the treatment of scopes change somehow in Virgo 3.0? Don't see anything relevant in http://wiki.eclipse.org/Virgo/Community/Migrating_from_2.x_to_3.0.0 (and of course there are still many dependencies in /repository/usr which are picked up even though they aren't listed directly in the plan)

This does look odd. I suspect that the problem is that the mina bundle imports and exports certain packages (e.g. the ...ntlm package). Import-bundle of mina will expand to include all the exports, but if any of these exports are dropped in favour of a matching import during resolution, then the generated import package will be unresolvable. This is a limitation in the way Import-Bundle is implemented.

However I'm not aware that anything significant has changed in 3.0 to make this behaviour different from 2.1.0. Perhaps your setup under 2.1.0 causes the exports to be preferred over the imports so that the problem does not occur.

The resolver chooses either the import or the export of a package that is both imported and exported by a given bundle depending on other exporters of that package. This can be affected by e.g. bundle install order.

Perhaps you could raise an enhancement bugzilla to cover this. If you can provide a cut down example to confirm that my theory is correct, that would be very helpful.