I'm running Eclipse (versions 3.6 and 3.5) on Ubuntu and I'm having trouble installing Eclipse plugins.
There is an easy way to install eclipse plugins in Eclipse, but this doesn't work for me on Ubuntu! This way only works properly under Windows and Mac OSX.
Just like in the tutorial, I create a folder inside my eclipse SDK folder that is named Links.
In this folder, I create a file eclipse-cpp-helios-linux-gtk.lnk or eclipse-cpp-helios-linux-gtk.link that contains this line:
path=/home/taher/opt/eclipse/Third-party-eclipse-links/eclipse-cpp-helios-linux-gtk
and save it, but when I start Eclipse doesn't recognize the plugin!
How can I resolve this problem?
With Eclipse Galileo (3.5) or Helios (3.6), I would rather recommend an external directory called 'mydropins' (for instance), which you can reference from your eclipse.ini, with the option:
-Dorg.eclipse.equinox.p2.reconciler.dropins.directory=C:/Prog/Java/eclipse_addons
This is called a shared dropins folder.
See in this SO answer an example of plugin deployment in this shared dropins folder.
(Your link refers to the previous provisioning mechanism, pre-p2.
P2 is the new provisioning system introduced late in Eclipse3.4, refined (debugged?) in eclipse 3.5 and 3.6.
See the supported dropins formats to check how you can organize your own personal dropins folder (that you can reuse between several eclipse installations)
You said you are using:
-Dorg.eclipse.equinox.p2.reconciler.dropins.directory=/home/taher/opt/eclipse/Third-party-eclipse-links
That means, under /home/taher/opt/eclipse/Third-party-eclipse-links, you:
won't have any .link file
will copy:
eclipse-cpp-helios-linux-gtk
eclipse
features
plugins
Note: the structure within eclipse-cpp-helios-linux-gtk should be the one describe above, for p2 to pick it up.
Related
I'm developing an eclipse plugin and in order to test it I have to install it into my eclipse application regularly. However as I dont't want to change the version of my plugin every time I want to test a new feature I always uninstalled the plugin from within eclipse and afterwards I'd go to the eclipse folder and delete my plugin out of the plugins folder (and delete the respective entries in the eclipse XML-files).
That worked great in windows but I have recently switched to Linux (Mint) and I just found out that my plugin is no longer located in the plugins folder inside the eclipse program directory. Therefore I can't really delete the old plugin whcih then prevents the new version of the plugin from installing properly.
Does anyone have an idea about where eclipse copies the installed plugin or a differerent approch to actually completely uninstall (delete) an installed eclipse plugin?
Okay after searching through my whole filesystem I found it out myself.
Eclipse has a hidden folder in the home directory named .eclipse in which each installed eclipse version has it's sub-directory and in there there is also a plugins and a features folder that then contain the externally installed plugins and features.
It also contains the corresponding artifacts.xml.
I'm not sure whether this behaviour is specific to the Linux Mint OS or rather a new "feature" of Eclipse Neon but if anyone is having the same problem that's were I found it.
Help -> Installation Detail.
Then click the plugin you want removed then press "Uninstall...".
Note: there is a "Plug-ins" tab in the Installation Detail dialog. This is misleading; you are not to click it.
Ps. It might be easier to test the plugin, during development, on a run-time workbench.
The emacs documentation http://www.gnu.org/software/emacs/manual/html_mono/ede.html#Android-projects mentions that global-ede-mode supports android projects.
It mentions a function to declare the android sdk location, which I cannot find in emacs.
It also mentions that ede includes tools to interface with android tools, such as build and run emulators. These tools I cannot find either.
Has anybody had any luck using emacs built in ede mode to access android projects?
Currently running lubuntu 14.04 with emacs 24.3.1
The Android support for EDE is part of the CEDET project at http://cedet.sf.net, but that part wasn't included during the last merge from the CEDET repository into Emacs. Apparently that support wasn't removed form the manual. :)
If you download the sources from bzr, you will discover lisp/cedet/cedet-android.el, and lisp/cedet/ede/android.el which is the the support you found described in the manual.
In theory, you might be able to pull those two files down from bzr and just add to your own lisp repository, though it is always safest to download the entirety of the CEDET code and use it's install mechanism to ensure everything works correctly.
Once installed, you will find that the Development menu as project and target options that list things like starting up the debugger, or easily navigating between different .xml sources and your java source.
I have multiple eclipse SDKs installed on my linux notebook. They are in different directories and I do not remember which is the last one I installed. The command 'which eclipse' gets me /usr/bin/eclipse. /usr/bin/eclipse is a shell script that (among other things) sets ECLIPSE=/usr/lib/eclipse/eclipse. /usr/lib/eclipse/eclipse is a real executable (not a link) that was copied in from elsewhere.
The command 'eclipse' brings up a functioning eclipse. My question is: If I want to expand the capabilities of this eclipse, which SDK do I need to make changes to - ie which SDK do I insert add-ons? That is, given an executing eclipse, how do I find the sdk?
On the Help > About Eclipse dialog click Installation Details for lots of details about the installation. The Configuration tab contains the paths of what is being used.
Adding to Eclipse is generally done using Help > Install New Software and you don't normally need to know where the Eclipse install is for this!
We are trying to setup Eclipse in a shared environment, i.e., it will be installed on a Linux server and each user connects to it using remote X. There are different reasons for sharing Eclipse, one being proper integration with ClearCase.
Our admin has setup eclipse with some default plugins and each user accesses eclipse thru remote X. Now, I wanted to install a new plugin so that it can be used by everyone. After installing the plugin, it's accessible to me only, it's not available for others. However, the plugins installed by admin are available to everyone.
When looked, the plugin installed by me and the plugin installed by admin are at different location:
plugin installed by me:
/home/ernesto/.eclipse/org.eclipse.platform_4.2.0_53742576/plugins/
where /home/ernesto/ is my home directory.
plugin installed by admin:
/project/eclipse/plugins/
where /project/eclipse is eclipse installation directory
Is it due to permissions? Is this behavior documented somewhere?
I am using eclipse juno 4.2, it's SuSE Linux server.
You are right. It's due to permission restriction.
You can find detail information from Eclipse's documentation.
Note: There are a lot of existing known defects in this scenario.
I want to use a different installation of the Eclipse IDE, and drop into it some plugins and features that I already downloaded and install on a different instance of Eclipse. How can I do that? AFAIK, it's not as plain as copying the jar files, because Eclipse keeps some meta-data somewhere.
If it matters, the OS is Ubuntu Linux.
The convention is for the meta-data for plugins to be kept in workspace/.metadata/.plugins/ So just copy those to the workspace for the new install. Or just copy the entire workspace if you like.
You can try adding the old eclipse as a repository for install new software. The directory you want is OLD_ECLIPSE/p2/org.eclipse.equinox.p2.engine/profileRegistry/SDKProfile.profile/
If you uncheck "group items by category" you should see the list of features you installed in your OLD_ECLIPSE.