[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[platform-update-dev] Optional dependency is not resolved after update.
|
Hello,
I have the following scenario:
- install plugin A that have optional dependency on plugin B version X.X.X
or greater (plugin A checks whether plugin B version X.X.X or newer) is
installed and uses its API if it is there).
- restart Eclipse when suggested.
- install plugin B, version X.X.X
- restart Eclipse when suggested.
- NoClassDefFound exception from plugin A (it detects that there is a bundle
for plugin B, but couldn't access its API).
- restarting Eclipse with -clean option resolved the problem.
Is it known issue? Could you suggest any workaround (except for restarting
with -clean option or using non-optional dependency)? Thanks!
I've tested it with Eclipse 3.3.M5eh and Eclipse 3.2
Alexander Kitaev.
--
View this message in context: http://www.nabble.com/Optional-dependency-is-not-resolved-after-update.-tf3526423.html#a9839148
Sent from the Eclipse Platform - update mailing list archive at Nabble.com.
