Actually, even better would be to try
to remove the indirect references. I opened the following 2 bugs
on webservices & j2ee and applied patches which remove the references
in some of the plugins. I'll be honest, I did not actually test the
patches, but it seemed pretty straight forward. It seemed like some
of the errors were flagged on calls to org.eclipse.jem.util.emf.workbench.ProjectUtilities.getProject(String).
And really, that method just calls ResourcesPlugin.getWorkspace().getRoot().getProject(String).
So it seems like you can just replace calls to ProjectUtilities.getProject
with calls to ResourcesPlugin's getProject.
David M Williams/Raleigh/IBM@IBMUS Sent by: wtp-dev-bounces@xxxxxxxxxxx
04/04/2006 03:34 AM
Please respond to
"General discussion of project-wide or architectural issues."
[wtp-dev] Any body using M6 yet? See
"breakages" in our dev. env.?
I sure hope you are using M6! :) Especially since we are building
with it now!
If so, and if you have all/most of our WTP plugins loaded, have you noticed
there's a ton of new errors? similar to
"The type org.eclipse.core.resources.IResource
cannot be resolved. It is indirectly referenced from required .class files"
Which results in nothing much building (in the workspace, builds fine in
batch mode, and runs fine).
I'm not sure what changed to cause this change, or what "right"
But, the easiest solution is to add things like core.resoruces to the manifest.mf
core.resources is probably easy and obvious ... everyone needs that, right?
but emf.ecore was another that will have to be added to some... that's
less desirable to "require", I'd guess.
See also for some similar issues and pros and cons.
Anyone else want to propose a solution? _______________________________________________
wtp-dev mailing list