I need to install eclipse plugin required by Test and Performance Tools Platform (TPTP).
When I downloaded EMF Runtime, I have two directories: one is feature and the other one is plugins.
Then, what is the next step for installing them into eclipse?
My eclipse installation has directories including features/plugins and dropins. Is the plugin installation is just copying the files into feature/plugins directories and restart the eclipse? Or do I need any other step for the installation?
just copy and restart eclipse. if you get problems with eclipse, then start on command line with "eclipse -clean"
Related
How to manually install "veloeclipse" plugin in eclipse luna (4.4.0) other than install wizard available in eclipse?
In general if you would like to manually add a plugin to eclipse you can use the dropins folder.
Step 1: Download the Plugin
Step 2: Unzip the file, you should see
two folders, features and plugins
Step 3: Copy those folders
directly into the /dropins folder (this folder is within your eclipse
installation. e.g: C:\DevApps\eclipse\dropins
Step 4: Restart Eclipse
Step 5: Plugin will be installed, check Help -> Installation Details
-> Plugins
You can either use
Eclipse Directory Application
Allows installation via script on commandline
Eclipse Dropins Folder Just throw the plugins into a specific folder
I am trying to download and install PMD plugin for Eclipse offline but did not succeed in doing so.
I downloaded following 2 zips:
net.sourceforge.pmd.eclipse-3.2.6.v200903300643.zip (this version matches with the one which I installed online)
pmd-eclipse-1.8.0
Not sure which one to use and how to configure it in Eclipse.
I searched a lot but did not find proper steps for the offine installation and configuration.
In case it contains site archieve:
Goto Help->Install New Software
Click Add...
In the Add Repository Dialog click Archive and point to your zip. Rest of the installation is as you would do with an online installation.
Else:
Extract the zip
Copy all plugins to your target eclipse plugins folder
Copy all features to your target eclipse features folder
launch eclipse with -clean option
You can get the latest 4.0 version of the plugin by pointing your Eclipse installer here:
http://sourceforge.net/projects/pmd/files/pmd-eclipse/update-site/
I have installed cdt-master-6.0.2.zip (link) to my Eclipse by extracting it to the Eclipse installation dir. I'm using Eclipse 3.5 in Windows 7 x86 machine. But the plugin doesn't show up when I start Eclipse (I can't create a new cpp project). Yet cdt shows up in Help > About Eclipse SDK > About Eclipse SDK Features. What am I missing here?
To install plug-ins into Eclipse you should always prefer using the user interface through Help > Install new software menu.
Anyway if you really want to install plug-ins manually into your Eclipse installation, you have to place them into the dropins folder.
BUT this way you will have to resolve plug-in dependencies by yourself. If all dependencies are not satifsied, the concerned plug-ins will fail to start silently. This is why you should REALLY prefer to use the standard plug-in installation method to avoid any problem.
I was hoping to use the Qt plugin with Eclipse. The installation is very simple - just expand a tarball in the appropriate directory. After doing so, I can see trolltech folders under eclipse/features and eclipse/plugins. However, when I try to create a project, I see no sign of any Qt option. Nor do I see Qt listed in the Installed Software listing of plugins or features.
Eclipse: Galileo Build 3.5.2
CDT: 6.0.0.2
O/S: Ubuntu 10.10 i686 2.6.35-28-generic
Plugin in tarball: qt-eclipse-integration-linux.x86.1.6.1.tar.gz from here: http://qt.nokia.com/developer/eclipse-integration/
Starting Eclipse with -consolelog -debug didn't offer any enlightenment
Have the Qt plugins aged past their use-by date?
Update
Installing to /usr/share/eclipse is a mistake
Installing to /usr/lib/eclipse works
I would suggest that that the instructions on the Qt page could use some revision. Instead of saying:
Find your eclipse/plugins folder
It might be better to add: The eclipse folder should contain the eclipse executable, eclipse.ini, the plugins directory, and the features directory.
This would have kept me from being fooled by /usr/share/eclipse, which has a feature directory and a plugins directory, but is not the correct place to install additional plugins.
Try untaring under the dropins directory instead. Modern versions of Eclipse will not pickup plugins overlaid over the existing plugins and features directories. If dropins doesn't work then these plugins declare dependencies on older versions of eclipse components.
Find out where your eclipse installation lies in terminal. I have mine extracted to ~/tools/eclipse/
$ which eclipse
Navigate to the folder and extract the plugins into the plugins folder, the features into the features folder.
Start Eclipse back up and go to Window->Preferences->QT. Click Add and navigate to the executable directory. For me as of version 4.8.1 it was in /Qt/Desktop/Qt/4.8.1/gcc/bin. The includes directory auto updated to /Qt/Desktop/Qt/4.8.1/gcc/include, click Apply and restart if necessary.
After this I can create a new Qt Gui projects, Qt gui classes, Qt resource files and Qt console projects in addition to Qt Designer forms.
With the new Eclipse 3.5.2 Update manager, I am not able to find, how do I specify installation directory for my plugins. I use it, so that I can manage multiple installation of eclipse, without installation plugins again. Can anybody provide me settings, so that I can specify location for plugin, while installing it ?
You can use an external dropins folder, with the setting (in your eclipse.ini):
-Dorg.eclipse.equinox.p2.reconciler.dropins.directory=C:/jv/eclipse/mydropins
Now, the trick is:
If you install a new plugin through Eclipse itself, it will install it directly in its own plugins/features internal directories.
It is up to you to move those jars in a similar directory structure in your external dropins directory.
So this is not an exact solution for your problem, but at least that allows you to isolate those plugins in a shared external directory which will be read by different Eclipse installation on each Eclipse session startup.