I have installed eclipse checkstyle plugin. It installs properly but is not showing up in windows -> preferences. Currently using Mars.2 version. Have tried installing from both the update site http://eclipse-cs.sf.net/update and offline archive zip file and both install smoothly.
I have tried uninstalling, restarting eclipse in admin mode and installing again; and restarting ecplise with -clean -refresh options. None of these solutions have worked for me.
Am I missing something here?
As long as Mars is an old release, there may be some incompatibility problems between it and the plugin. You should check Eclipse Neon, where plugins should work without those issues.
If installation works but a plug-in then doesn’t show up in the UI, it may mean that its OSGi bundles fail to resolve. To check that, launch Eclipse with the -console switch; this opens the OSGi console in the terminal you used to start Eclipse with. Then, type the following:
ss | grep INSTALLED
This way, you will get a list of bundles that are merely INSTALLED but not RESOLVED or STARTING. If a Checkstyle bundles is among them, you have found your problem.
You can obtain further information suitable for a bug report to the Checkstyle developers by typing
diag $NUMBER
where $NUMBER is the number listed in the first column of the INSTALLED bundle.
Related
Overview
I am running Ubuntu 15.10 with Eclipse Mars 4.5.2 (from the Oomph installer) and and Java 1.8 and Python 2.7. I am attempting to the PyDev 5.2.0 plugin for Eclipse. Installing with Eclipse's update manager seemed to go okay. The only problem is that I can only see PyDev related options when I run Eclipse with sudo.
What I have tried
I made sure to set the java VM path in the eclipse.ini file so the Eclipse binary runs with Java 8.
I added Java 8 to Eclipse's JREs and set to be default.
I tried running the Eclipse binary with the -clean option.
The first two didn't allow me access to the PyDev options in Eclipse. Running as a normal user with the -clean option did let me see the PyDev options, but running as a normal user without -clean made the PyDev menu options invisible again.
Finally, I noticed that running Eclipse as root made the PyDev options appear again. This suggested that there was some ownership or permission problem. Since my Eclipse installation and plugins are in my home directory, I made sure my user has ownership over everything in the home directory. I also reviewed the permissions of files related to the PyDev plugin, and it appears I have the appropriate permissions, but since I do not know which permissions each file ought to have, I am not sure.
I am not sure what is going on. It is especially surprising given that I was able to install the CDT plugin not long ago without any hassle. It's also possible the problem might be related to how root's environment is configured compared to my user's, but being able to access PyDev when running with -clean seems to vanquish that theory.
I could just run Eclipse as root from now on, which isn't that big of a deal. However, it is quite annoying not knowing why this is happening, making me feel like I don't have control over Ubuntu and Eclipse.
My guess is that you have the eclipse configuration folder not accessible by the current user (or some other folder inside the .metadata).
Try verifying/fixing the permissions on those folders (I don't exactly know where those folders go on the default ubuntu install, but on windows it's eclipse/configuration and the .metadata is where you point your workspace to).
In my case, upgrading to Ubuntu 16.04 solved my problem. After the upgrade, PyDev was working normally in Eclipse.
I'm struggling to get the Eclipse FindBugs plugin to work and am sure there's a schoolboy error being made somewhere.
I extracted the file findbugs-2.0.2-rc2.zip to a local folder C:\Program Files\findbugs-2.0.2-rc2 and running findbugs.bat, FindBugs works fine running it over a local Java (Eclipse) project.
I added the FindBugs update site, it found "FindBugs Feature, 2.0.1.20120712" and installed it. Restarting, right-clicking on an open Java Project doesn't display the "FindBugs" option (that this video shows).
I looked in Window > Preferences to try to find a way to inform the plugin of the local FindBugs installation (in Program Files), but couldn't find anything.
Uninstalling "FindBug Feature", I tried extracting the FindBugs Eclipse plugin zip file into Eclipse's plugins folder, but after a restart, saw no difference.
Help > About Eclipse > Installation Details > Installed Software lists "FindBugs Feature 2.0.1.20120712".
Can anyone please offer a pointer on where I'm going wrong here? Thanks!
Windows 7, Eclipse IDE for Java EE Developers Juno SR1, JDK 1.7.0_09, FindBugs 2.0.2-rc2
As suggested above, problem is likely caused by not having appropriate write access to the C:\Program Files\Eclipse\plugins folder.
Solution:
Close Eclipse. Restart Eclipse as Administrator (right click - Run as Administrator). Reinstall plugin. Restart Eclipse.
It looks like the Findbugs plugin wasn't installed properly and/or disabled by Eclipse. There can be several causes.
Multiple versions of the same plugin. To make sure this isn't the case, remove all Findbugs versions (installed manually and via the marketplace), and reinstall one (preferably via the marketplace). Watch for any warnings during installation.
There is a (dependency) conflict with another plugin. However, if this is the case I think Eclipse will warn in the log which other plugin is the cause of the conflict.
Rights problem. Make sure you have write permissions in the main Eclipse folder and all it's child folders.
I remember reading somewhere that installing Eclipse under the C:\Program Files\ in Windows can also be causing problems. Try moving Eclipse to a different folder, e.g. C:\Eclipse
Hi I also faced the similar problem but from my own experience i can suggest you the solution :-
Plz ensure that you are using eclipse version 3.6 or higher. findbugs 2.0 is not compatible with Eclipse 3.5(Eclipse Galileo).
1) Plz extract the findbugs zip file into eclipse folder(wher your eclipse is installed). This will automatically move findbug plugins into eclipse plugins folder. Restart the eclipse and you will find findbugs option on right clicking on project.
2) if 1 step does not work plz remove all the findbug jars for the eclipse plugins folder and place the complete folder into the eclipse dropins folder. Restart the eclipse and you will see the difference.
You can follow these step's to make findbugs work in your eclipse.
1.Install FireBug plugin from marketplace.
Help->Eclipse Marketplace ->then search for FindBugs
2.Configure FindBug for your project
using Maven Without Maven
This worked fine for me using eclipse juno.
I recently updated my ports on my FreeBSD 9.0 release machine and I think eclipse was upgraded due to a port upstream forced Eclipse to be rebuilt. Now Pydev is gone. I tried uninstalling then reinstalling Eclipse, then installing Pydev using pydev.org/updates inside Eclipse. It appears to install ok but I can't create a Pydev project or use the Pydev view. I tried removing my ~/.eclipse folder to force the creation of a new one, and reinstalling Eclipse and Pydev to no avail. What am I doing wrong? I'm running Eclipse Indigo version 3.7.1 build id: R3_7_1
This question was most similar to mine, but the solution didn't work for me. I also tried pointing my install site as: http://update-production-pydev.s3.amazonaws.com/pydev/updates/site.xml per another question on StackOverflow, to no avail.
After some more testing I finally got the newest FreeBSD port to work. I had to launch and install the plugins as root. It didn't work another time I ran it but, this great troubleshooting document helped out. I methodically went through each step one by one, and the logs indicated there was an error on my /usr/local/lib file it was trying to unzip. My user doesn't have write access to that directory but root does. I don't know why it didn't work the last time I ran it as root, perhaps I didn't install the plug-in as root. It works now, so I'm happy. Thanks Fabio, for your input.
I'm not sure how FreeBSD packages things, so, maybe an easy way out would be getting Eclipse from Eclipse.org and installing PyDev on that fresh install (or if you're also doing web stuff, I'd suggest grabbing Aptana Studio 3, which comes with PyDev preinstalled, so, you don't have to worry about configuring it).
See: http://pydev.org/download.html for details
I'm sorry for a pretty vague title, didn't want to turn it into a paragraph.
So, I am using Eclipse Platform 3.7.1 (the one with absolutely no plugin preinstalled), the latest version so far, and I have discovered that by taking advantage of its -configuration option, I can choose which plugins are running and which are not. It was going well enough until I started installing the plugins.
But allow me to explain my setup first, I am using Ubuntu linux by the way. Using only one eclipse installation, my installation is arranged in the following order:
Installation:
~/bin/opt/eclipse
eclipse (executable binary)
~/bin/eclipse -> opt/eclipse/eclipse
Configurations:
~/.eclipse/configuration
web-php
android
java
Installing JDT and ADT while running eclipse and using the android configuration directory posed no problems. So I moved on to the php configuration and tried to install PDT (the JDT and ADT plugins were not activated here, so far so good). The problems came along after the installation, not only was I not able to use PDT, I noticed in the Installation Details that JDT, ADT, PDT were installed but not activated. Instead, they were all activated in the android configuration. To make it worse, when I chose the Java configuration, I could not even use JDT.
My expectations however were when using:
eclipse -configuration ~/.eclipse/configuration/android
was that only the JDT and ADT were activated and when using:
eclipse -configuration ~/.eclipse/configuration/web-php
only the PDT is activated
Regarding the java configuration however, it's probably another problem altogether but if there was help on how to activate a plugin installed from another configuration, I'd deeply appreciate it.
Also, see Single Eclipse install with multiple Configurations and Workspaces
In a p2 world there are extra steps to isolate bundles from each other. You need not just a different configuration directory, but a different p2 profile.
Have a look at the config.ihi in each of your configurations. There are two ways that Eclipse identifies the plugins to use, the ..updateconfigurator, which simply uses all of the plugins in the plugins folder, and the ..simpleconfigurator which uses the bundles.info file in that's in the org.eclipse.equinox.simpleconfigurator folder (which is maintained by the p2 installer). Make sure this file is what you expect.
And also, you might want to start with the -clean option if you are using the updateconfigurator to have it rescan all of the plugins (otherwise it remembers in some hidden cache).
Make sure when you installed everything that you had your -configuration set to the right place for the different things you installed.
I hope some of this points you in the right direction.
I am new to Eclipse so I am having a hard time troubleshooting this problem. I have a new installation of Eclipse Java EE - Galileo on Windows, and I am unable to see any changes made in the IDE after installing plugins. I have verified that the plugins are installed via installation details, but see no changes made.
For example, after installing the maven integration plugin m2eclipse I go to File->New->Project ... and I have no option for maven. After installing the QuickRex plugin I have no view for it etc.
I have tried re-installing the plugins, re-installing Eclipse, and starting Eclipse with the -clean option, but nothing has resolved the issue.
Any ideas? Thanks!
Ok. This is just a wild guess but could you start over with a fresh install and make sure that you uncheck the option Contact all update sites during install to find required software as shown below:
alt text http://img717.imageshack.us/img717/8039/screenshot003ao.png
I faced a similar problem (on another platform than yours), some updates were "disabling" all my plugins. Not checking this option allowed me to work around this issue.
Follow-up: You'll need to install that Zest stuff manually from the GEF update site:
alt text http://img339.imageshack.us/img339/8003/screenshot003rl.png