osx - Problem in plug-in development: Eclipse 3.4 can't find a bundle that is definitively there! -
Today I had a problem with my old Eclipse 3.4 installation and I had to download the entire package again. However, I do not think I have received the exact package as before, and I have some problems.
This problem can be summarized as follows: When the plug-in is developed, I can not resolve Dependencies on 'org.eclipse.jdt.ui' When attempting to add a plugin, the closest match in the dialog is 'org.eclipse.jdt.ui ** ** Source **'. Nothing similar happens with other core plugins.
For testing, I have created a new plug-in using the magician and I have received a non-compiling plugin: one class from classes Org.eclipse.jdt.ui .JavaUI and it can not be resolved. Similarly, MANIFEST.MF includes dependence on 'org.eclipse.jdt.ui', but ' bundle' org.eclipse.jdt.ui 'can not be resolved '.
Now the essence of my forum:
- I'm running Mac OS X 10.4 Tiger and Java 1.5.0_19-138
- I'm running Eclipse version: 3.4.1 Build id: M 20080 9 11-1700
- I've downloaded the modeling package, which is the 'Eclipse-modeling-gunmyd-SR1-incubation- Macaux-Carbon .gz '
I have a fresh installation in a new folder and using a new workspace.
If I see see the plug-in registry , I can find the 'org.eclipse.jdt.ui' plugin there, and it appears to be running. By the way, if it is disabled, then the workspace breaks down and stops working.
I do not understand what's going on. Is my establishment broken? I am surprised if the downloaded eclipse package has an error and they have included sources instead of the compiled files, but in that case, the plug-in should not work in the workspace, right?
In any case, when I am adding dependency, why can not I get the plug-in, even if I see it in the plug-in registry?
Thank you for your help!
Problem Solving: Just restart the computer.
I do not restart my computer very often, so I took a lot of time to find out that this was the solution. After I restarted it, everything started working completely again. It seems that either leaves something in memory after assuming or some of my initial failures left behind some disturbances. In any case, I checked and there were no eclipse procedures ... odd, but at least now it is fixed!
Comments
Post a Comment