> hmm, sounds like a bug in Eclipse - if you're changing a class and > have other projects in your workspace that reference that class then > why won't it refactor them? unless it's just going by the > "requiredPlugins" dynamic container (PDE projects don't typically > contain direct project references)
I'm not so sure it's a bug, but rather the normal behaviour. Why should PDE magically know that a project in my workspace is the same as a referenced project that is in my maven cache? > could you try using the original generated .classpath file, but move > the > "requiredPlugins" entry up so it's before the rest of the > dependencies? > then try refactoring - this might work because then PDE will check its > dynamic container before the explicit maven references There is no "requiredPlugins" entry. Could this be the problem? And please, no more IDEA jokes. It's not funny any more. ;-) Cheers, Dave _______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
