It seems to be a common problem with Eclipse CDT on Windows that Eclipse uses the Windows "del" command to perform a "clean", while using Unix-style paths and rm options. The workaround, at least for the Juno release, is to force Eclipse to use the GnuUtils rm instead: Editing .cproject to change the clean command
I had the opposite problem - Eclipse insisted on running "del" in a project using the GNU toolchain and MinGW build tools, which did not work. Therefore, I edited .cproject to force the use of rm.
Is this the only way to do it, even in newer releases of Eclipse, e.g. Neon? I would expect that Eclipse has a built-in control for this setting, but I browsed through the project settings and through the online help without finding any.
Related
I'm at my wits end with this.
I have a project I want to edit with the Eclipse CDT IDE, but it requires a more recent version of cmake than my distribution provides. I have a (verified working install) of the latest cmake in my home directory, but I cannot for the life of my figure out how to make Eclipse detect or use it.
I have tried every combination of changing eclipse's build environment variables I can possibly think of. I've tried the linux tool path setting. I've even tried adding my personal install of cmake to the global PATH and then nuking eclipse's setting and completely reinstalling. Nothing has worked, it's like it's hardcoded to /usr/bin/cmake.
How do I get it to use a different cmake binary? Preferably per-project, but I'd settle for a global setting at this point.
I have installed Eclipse Juno on a linux machine and am trying to set up PyDev.
I have installed PyDev using Help => Install New Software, and it seemed to work fine and is listed as installed:
However, I do not find PyDev under Preferences, and I don't find the PyDev Perspective.
Any suggestions on how to get this running? (I'm normally a Windows user...)
You could be in a custom perspective in which the plugin commands are not set to be visible How To Add Perspectives In Eclipse
Another way:
sudo eclipse -clean;
Help --> Install software --> Re-install the plugins and software;
Explanation:
Eclipse is installed and the majority of programs are also installed initially with root privileges.
Typically 'Ownership' of hidden install folders like this belong to the 'sudo' or Root user. Therefore changes and installs to these hidden folders will not take.
Your requisites aren't Ok. PyDev 5.6 requires Neon (Eclipse 4.6).
See: Need to use older Eclipse/Java/Python in http://www.pydev.org/download.html for details on the PyDev version you need for older versions of Eclipse (also, make sure your java version matches the requisite).
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.
When I run maven release:prepare from the command line I'm prompted for the release version, developer version and SCM tag. This is good. What is not so good is when I do the same from inside Eclipse. Using an m2e run configuration I set the same goal but instead of prompting me for the version information it automatically sets them to some defaults. The defaults are pretty good but sometimes I want explicit control.
There are many developers on this project and asking them to drop out to command lines or fiddle with shared run configurations is not ideal. Maybe this has nothing to do with the Maven Release Plugin and is more to do with input prompts in general. Are there any other examples of Maven plugins prompting for input during execution inside Eclipse?
I'm using SpringSource Tool Suite 2.9 (old!) configured to use an external Maven 3.0.3 with m2e 0.12.1.
This is normal. The Eclipse plugin for Release will automatically release the version set in your POM, and set the next development version to +0.0.1 of that.
I'm used to using the release plugin from inside Eclipse, and when I used it from command prompt I was surprised when I was prompted for version :p
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.