I just installed Eclipse Neon. I also have Eclipse Mars still lying around on my system. When I opened Neon it asked if I wanted to convert my workspace and I did.
So I installed PyDev through Help/Install on Neon and now I go to File/New/PyDev Project and follow the prompts to create a new Python project. It does not show up in PyDev Package Explorer. If I try to create it again with the same name, it says I cannot because the project already exists.
When I first installed PyDev, 3 projects showed up in the PyDev Package Explorer, but they all contain folders underneath which cannot be expanded so I don't think those 3 projects are being handled correctly either. Actually they are closed projects I see, but I see at least 1 is a Java project, so it does not belong to that perspective.
So any idea why Neon/PyDev is not handling my Python projects correctly?
So from the above comments, there were two defaults for PyDev Package Explorer I was not expecting when I installed Neon (which may well not just apply to Neon, but other versions as well)
Display working sets was the default behaviour and I wanted display projects.
I wanted non-Pydev projects filtered out and they were not
Related
I'm in trouble with Eclipse configuration. I had Eclipse Juno with a certain configuration (perspectives, opened views like Logcat, console, etc), I removed it from my system and downloaded Eclipse Luna.
When I opened it the first time and selected the Workspace, Eclipse loaded the perspectives used in Juno (for example Remote System Explorer) but those perspectives weren't installed in Eclipse.
This also happens with the Logcat view, Eclipse Luna hasn't installed ADT (Android) and Logcat wasn't available.
Why is this configuration loaded if I removed Eclipse completely?
The workspace contains the information about the perspectives, views, ... in use.
So if you install a version of Eclipse without some of the plugins you were previously using you should probably create a new workspace. You can import your projects from the old workspace (but if the projects reference any of the old plugins you may get errors).
I have an Eclipse plugin that was originally written (not by me, and I don't have access to the original developer) that I'm trying to update for Eclipse Luna, because it stopped working when my team updated to Eclipse 4.4.
I downloaded the Luna Plugin development version, cleared a few warnings, updated some broken code, fixed a few bugs, and tested with "Run As -> Eclipse Application
This worked fine: all the views showed up, the preferences pages, etc.
So then I tried to export the plugin so I could test on a fresh installation of vanilla Eclipse Luna. I did that by using the Export Wizard:
And generated a deployable set of jars with said wizard:
I copied the generated folder (which contains all the jars appropriately) into the dropins folder of my fresh vanilla Eclipse Luna and started it up.
Unfortunately, I got the following error:
Which led me to this SO question and this Eclipse bug report, which explains that I have a 2.x style plugin that uses the plugin.xml instead of an OSGi style manifest.mf. Continuing my search, I found this SO question, which was directed at a 3.x version of Eclipse, but I used the 4.x equivalent:
Which I used with the following options checked:
And I accepted all the changes in the previous pane after the (long-running) changeset. However, upon deploying to my vanilla install, I got the same error about the plugin converter. That led me back to this SO question, which recommending installing the Eclipse 2.0 plugin support package. I did so and restarted Eclipse. The error in my error log did stop showing up, however the view/preferences/etc for my plugin are still not showing up. The plugin does show up under Help -> Installation Details -> Plug-ins, but doesn't seem to be interacting at all.
The text of the plugin.xml can be found here at Pastebin. The text of the MANIFEST.MF can by found at this other Pastebin link
Any suggestions for getting my plugin to work through the manual export so the other developers on my team can test my changes before I try releasing the update to the world?
I'm using Ubuntu 12.04, and to install Eclipse Juno I downloaded it from the official site (I don't use apt-get nor software center)
After updating it from help > check for updates menu, my Eclipse cannot make new project. When I hover File > New, there isn't any menu to select (as the usual Java Project, C++ Project etc.), only an unselectable text like this:
< No Applicable Items >
Anyone know what causes this?
nitind's answer above helped solve my problem. I was using eclipse java ide juno on windows and i could not see any items under File -> New or under Window -> Show View. I noticed eclipse had defaulted to using the Java-EE perspective. Following nitind's suggestion I changed it to the Java perspective and can now see all the menu items. thank you!
I had the same error when i first started the program, but i looked into it, and I saw that the workspace already had .cpp and compiled files in it which i had compiled earlier with a different program. To fix the error, I just changed the workspace to the default, and it worked fine.
I was using eclipse CDT Kepler with java 1.6.0_27. I then tried it with java 1.7.0_25 and eclipse Juno and this method resolved the error in any of these instances.
Try using the default workspace and it should work.
Regards,
Nikita
I have Eclipse IDE for Java Developers (Indigo) and have been using it for several months.
I had many installed plugins including a SVN one and e-git.
Then one day, they just all stopped working. For example, I used to be able to commit from the Explorer (using the SVN plugin), but that option has disappeared as if it is not installed.
I have checked the installed software list and they are all present.
Is there a setting somewhere that I may have miss?
Thanks in adavnced!
Please check the error log in workspace/.metadata/.log to see if there is any warnings or errors.
Also, have you tried other perspectives, like plug-in development, or SVN.
Open eclipse
Go to Window -> Show view -> Other -> SVN
Choose new workspace and check out the project that you did
I've got my Eclipse 3.4 envirnoment set up nice and cozy the way I like it. Took me some time too, to find all the plugins (Mylin, PDT, Subclipse), set all the settings, etc. Now I see that some of the plugins (like PDT) only support 3.5 in their latest versions.
Is it possible to update from 3.4 to 3.5? I'd hate to do it all again.
I read in some mailing list where they noted that it's possible, but the conversation trailed off in another direction. Google wasn't much help, and Eclipse's documentation either.
All of your settings are actually stored as part of your workspace. So you could do a fresh install of the latest version of Eclipse, add the extra plugins that you want (many of which will have newer versions for Eclipse 3.5) and when you launch, just make sure you point to your old workspace.
Help -> Software Updates... -> Available Software tab -> Add Site...
Enter the update site for the Galileo (3.5) release train: http://download.eclipse.org/releases/galileo
Now go back to the Installed Software tab and click the Update... button.
After some computation you should be presented with a list of available updates (or some cryptic errors about how your current environment cannot be updated due to compatibility issues).
This is what I did.
1.- My workspace was in c:\Users\me\workspace.
I copied this folder to c:\users\me\eclipse\workspace-3.4 and to c:\users\me\eclipse\workspace-3.5
So now I have twice the same, just with different names.
2.- Extracted eclipse-SDK-3.5-win32.zip to C:\program files\eclipse-SDK-3.5-win32
3.- Run Eclipse 3.4 and changed the workspace from c:\Users\me\workspace to c:\users\me\eclipse\workspace-3.4. Then I closed Eclipse.
4.- Run Eclipse 3.5 and selected c:\users\me\eclipse\workspace-3.5 as the workspace location (you can also use the -data argument I think).
5.- Downloaded and installed the PDT plugin (I develop in PHP).
And "Voila", now I'm able to run Eclipse 3.4 and 3.5.
BTW, even if I had to install the PDT plug in, I didn't had to touch the configuration. It took the former one from the workspace folder.
There is some information at help.eclipse.org/galileo/index.jsp, look in Workbench User Guide\Tasks\Upgrading Eclipse.