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.
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.
I am trying to setup a development box based on Fedora 23. I am using Eclipse Mars for development, and Wildfly 8 application server. The goal is to be able to use Eclipse and Wildfly together, using only the system-provided rpm packages.
The problem: I cannot use Wildfly from Eclipse, because the server is in /usr/share, and owned by root. This is understandable, even preferable. AFAIK I should use wildfly-cp to create an environment, which can be used to run Wildfly as a normal user. However, I could not manage to do so yet.
I am looking for detailed instructions how to make it work from Eclipse.
I have a box running Win2k to support a few legacy applications that can't be migrated forward at this point that I'd like to manage for most part with Cygwin.
However, the current Cygwin installer requires Windows XP 3. The installer referenced by the good folks at at Cygwin Time Machine runs just fine, but when I attempt to configure any suggested circa release area and proceed, the installer errors out attempting to download setup-2.bz2.sig and setup-2.ini.sig.
The circa release area I'm attempting to use is here.
Directory listing is not enabled, so really can't tell you anything more than the fact that setup-2.ini and setup-2.bz2 are there, but their signatures are not. Seems to be the case for a random sample of other releases listed here.
Cygwin Time Machine was enormously helpful in resolving this issue. Essentially, my woes were caused by
attempting to draw in packages from the Cygwin's 1.7 "development" branch (the setup-2.* errors).
using a setup installer too fresh for my purposes.
Digging around the Internet Archive, I found the last installation page update in which Windows 2000 (1 June 2013) still supported and downloaded the cached installer (link to setup.exe).
Cygwin Time Machine suggested these alternatives:
ftp://www.fruitbat.org/pub/cygwin/setup/snapshots/setup-2.602.exe
ftp://www.fruitbat.org/pub/cygwin/setup/snapshots/setup-2.573.2.3.exe
ftp://www.fruitbat.org/pub/cygwin/setup/snapshots/setup-2.523.exe
However, the 1 Jun 2013 installer (link) is considerably newer, can make use of a fresher repository (I'm able to install python 2.7.3 rather than 2.5.2), and has the nice filter feature we're used to in more modern installers.
Finally, Fruitbats does not archive the signatures for the setup package lists. You run at your own risk.
To ignore signatures, run the setup installer with an -X flag, i.e.:
c:\...> setup.exe -X
That about wraps it up. I have a mid-2013 Cygwin 1.7 installed on Win2k Advanced Server SP4.
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.
I have installed the Netbeans 6.7 IDE with Java ME included, but cannot create a Mobile Application project from the Java ME category. When I select the project type the wizard stops at "Finding Feature" with the message:
Not all requested modules can be enabled:
[StandardModule:org.netbeans.modules.mobility.end2end.kig jarFile:C:\Program Files\NetBeans 6.7\mobility8\modules\org-netbeans-modules-mobility-end2end-kit.jar.
I am attempting to run this on Vista Home Premium. I have tried to run the IDE as Administrator with no luck.
I am at a loss for where to go next as I cannot seem to find any information regarding this issue. Even if you don't have the solution any insight into this error message would be helpful.
I am unable so far to get the project running via the Netbeans IDE install. I have, for the time being, installed the Java ME SDK which includes a very stripped down version of the Netbeans IDE for mobile development.
I originally had some issues starting the SDK as well on Vista. The IDE reported that it could not connect to the device manager on localhost. After some searching I found this link: Java ME SDK Startup Problem which suggests changing the hosts file localhost entry from IPv6 to IPv4. The fix worked perfectly and I can now compile and run code in the emulator.
This is not an optimal solution as the SDK does not include the visual design tools, however I am able to get a basic project going in the mean time.
I have given up on the 6.7 version and have instead located and installed 6.5.1. This previous version has been working just fine and seems to do everything I need.
I ran into the exact same error today while installing NB 6.8 beta. To resolve it we need to install two plugins:
Java Web Applications (as mentioned by Ali above) and
Sun Java System Web Server 7.0
Note that these two are part of the Category called "Java Web and EE" hence the confusion that we need to install Glassfish App Server. But we need these two plugins because they are required for debugging using breakpoints in emulator. Netbeans runs a web server when we do breakpoint based debugging.
Also note that the Java Web applications needs SOAP Web Services and JavaScript Debugger plugins to run and so these plugins are also installed when you try to install it.
You also need to install "Java Web Applications" plugin.
Tools->Plugins->Available Plugins
If the module is present, you should try unzipping it to check its content makes sense.
You should also be able to rebuild it from Netbeans sources.
You can also try to figure out why this happens by debugging the module loader inside Netbeans from its sources, using another IDE, presumably the latest version of Netbeans you can find without the issue.
If the module is missing, you might want to get the missing jar file from an installation of a previous version of Netbeans, see if it is compatible.
6.5.1 isn't missing any module.
back in version 5.5, the mobility module had to be downloaded and installed separately from the main IDE.
If you want to consider using Eclipse for developing your J2ME app...I've written a post related to that some time ago: here.