I've got my Eclipse 3.4 envirnoment set up nice and cozy the way I like it. Took me some time too, to find all the plugins (Mylin, PDT, Subclipse), set all the settings, etc. Now I see that some of the plugins (like PDT) only support 3.5 in their latest versions.
Is it possible to update from 3.4 to 3.5? I'd hate to do it all again.
I read in some mailing list where they noted that it's possible, but the conversation trailed off in another direction. Google wasn't much help, and Eclipse's documentation either.
All of your settings are actually stored as part of your workspace. So you could do a fresh install of the latest version of Eclipse, add the extra plugins that you want (many of which will have newer versions for Eclipse 3.5) and when you launch, just make sure you point to your old workspace.
Help -> Software Updates... -> Available Software tab -> Add Site...
Enter the update site for the Galileo (3.5) release train: http://download.eclipse.org/releases/galileo
Now go back to the Installed Software tab and click the Update... button.
After some computation you should be presented with a list of available updates (or some cryptic errors about how your current environment cannot be updated due to compatibility issues).
This is what I did.
1.- My workspace was in c:\Users\me\workspace.
I copied this folder to c:\users\me\eclipse\workspace-3.4 and to c:\users\me\eclipse\workspace-3.5
So now I have twice the same, just with different names.
2.- Extracted eclipse-SDK-3.5-win32.zip to C:\program files\eclipse-SDK-3.5-win32
3.- Run Eclipse 3.4 and changed the workspace from c:\Users\me\workspace to c:\users\me\eclipse\workspace-3.4. Then I closed Eclipse.
4.- Run Eclipse 3.5 and selected c:\users\me\eclipse\workspace-3.5 as the workspace location (you can also use the -data argument I think).
5.- Downloaded and installed the PDT plugin (I develop in PHP).
And "Voila", now I'm able to run Eclipse 3.4 and 3.5.
BTW, even if I had to install the PDT plug in, I didn't had to touch the configuration. It took the former one from the workspace folder.
There is some information at help.eclipse.org/galileo/index.jsp, look in Workbench User Guide\Tasks\Upgrading Eclipse.
Related
I need to set up my Eclipse IDE again and unlike when I first set it up I have issues with the Groovy software. I would need the Groovy compiler version 2.4, but can only select between 2.5, 3.0 or 4.0.
I used the same location as last time: https://dist.springsource.org/release/GRECLIPSE/e4.16
Also I tried other location which unfortunately don't work properly. I have the Eclipse version 2020-06.
Can anyone tell me what I do wrong this time or which configuration to adapt?
Thank you.
Download "Eclipse IDE for Java Developers" (2020-09 a.k.a 4.17) from https://www.eclipse.org/downloads/packages/release/2020-09/r
Note: The first link on the page gets you the Oomph installer which WILL NOT WORK. Use one of the links below. If there is "inst" anywhere in the name of the file you downloaded, try again.
The reason why Oomph breaks GRECLIPSE is that it will add an update site which will try to install the latest 4.x GRECLIPSE -> fail.
Unpack the archive somewhere.
Go to Help -> Install New Software.
Add this update site: https://dist.springsource.org/release/GRECLIPSE/3.9.0/e4.17
(Using the marketplace will leave you with GRECLIPSE 4.x)
Always select the main package and Maven support if you need it.
Click Next.
Make sure that it tries to install 3.9.0 and nothing else.
Click Next & Finish until it installs.
--- old instructions for reference ---
You will need to download Eclipse Photon from here
https://www.eclipse.org/downloads/packages/release/photon/r
and then Groovy Feature 3.5.0.v201909291357-e48-RELEASE add this update site:
https://dist.springsource.org/release/GRECLIPSE/e4.8
All the versions of Eclipse after this one don't support Groovy 2.4 anymore.
I've tried to do this with Oomph but that way, I always ended up with Groovy Feature 4.1.
My solution then was to create another workspace for all my Groovy 2.4 projects (Jenkins Pipelines, mostly).
Have installed Eclipse Neon 3 x86_64 bit on macOS Sierra...
Proceeded by picking a workspace folder and installed the following plugins:
Subclipse 1.10.13 (by dragging the icon on to the workspace from https://marketplace.eclipse.org/content/subclipse)
Installed the following plugins (by going to Help -> Install New Software -> All Available Sites and expanded Web, XML, Java EE and OSGI Enterprise Development):
Eclipse Java EE Developer Tools 3.8.0.v201701262139
Eclipse Java Web Developer Tools 3.8.0.v201702270442
Eclipse Web Developer Tools 3.8.2.v201702270442
JST Server Adapters 3.2.400.v201606081655
JST Server Adapters Extensions 3.3.501.v201609071751
JST Server UI 3.4.300.v201606081655
Everything works (plugin functionality) but everytime I close Eclipse, it brings up the default dialog asking for a workspace and is completely fresh (no plugins and preferences...). I have to manually install these plugins every single time I restart Eclipse!
I've deleted the following directories and files:
~/.eclipse (folder);
~/Library/Saved Application/org.eclipse.eclipse.savedState;
~/Library/Preferences/org.eclipse.platform.ide.plist;
~/Library/Caches/org.eclipse.platform.ide;
And, also unzipped Eclipse into a different folder and specified a new workspace and after installing the plugins and restarting Eclipse, its completely fresh again!
This is very annoying and also disappointing...
I even tried to put -clean as the first line of the eclipse.ini file but it didn't help any...
What's weird is that this is happening on my company issued MacBook Pro but not my personal MacBook Pro (which is the exact same model and year as the company issue one)...
Any suggestions would be most appreciated!
Have you checked Eclipse Bugzilla for a similar issue?
It looks like you are running into this:
Bug 507328 - Eclipse forgets about global settings and installed features
It's a feature of macOS introduced with Sierra called "App Translocation" or "Gatekeeper Path Randomization". Try unzipping Eclipse and moving it (drag and drop) with Finder to a different location. This should set a flag which disables Gatekeeper Path Randomization. However, it's important this this is done from within Finder.
The Eclipse Oxygen packages will ship as DMG which will motivate users to drag and drop the Eclipse.app bundle into the Applications folder using Finder. There is an Apple bug here where Apple explicitly states that Finder may be able to opt an app out of Gatekeeper Path Randomization.
To check whether Gatekeeper Path Randomization is happing in Eclipse perform the following:
Open Eclipse > About Eclipse
Click Installation Details
Navigate to tab Configuration
Check the value of osgi.install.area property
If it points to some random looking path with /var/private that path randomization is in effect.
The situation may become more complicated in future macOS versions, though.
I do C++ embedded development for the NetBurner platform. They have plug-ins that customize Eclipse and in addition to a build tool-chain they add a Launch Group under the Run Configuration area. Everything was working fine under Indigo (32 bit) when I decided to install Subclipse (big mistake). As soon as the install finished I could no longer run my existing configurations successfully. When I went into the Run Configurations area I noticed the Launch Group I used to use was missing. Here is what it looked like earlier yesterday:
Here's what it looks like today:
Things I've tried
First I uninstalled the Subclipse plugins using the
Help->About->Installation Details and then selecting them one at a
time, Uninstalling and restarting after each uninstall. No change.
Then I unpacked the original Eclipse Indigo/CDT 32 bit download to a
fresh folder. Copied over the NetBurner plugins from the zip I got
from the manufacturer. No change.
Launched with different Workspaces, no change.
Launched a Galileo version, it uses older plug-ins, and it still
works.
Copied older plug-ins into Indigo, the older NetBurner launcher
shows up (but it doesn't really work with Indigo)
Removed the older plug-ins put in the newer ones, old NetBurner
launcher went away new launcher does not show up.
Tried removing the
{Workspace}.metadata.plugins\org.eclipse.debug.core.launches - no
change.
Interestingly even though launches has many .launch files that should show up under Run Configuration, nothing shows up.
One other strange (possibly relevant) thing is that icon for the NetBurner Perspective went away, now it just has <NetBurner> as the text and a generic perspective icon.
I can still cross-compile and build for the NetBurner (i.e. the build toolchain still works), it's just the ability to use run configurations that seems to be missing.
I'm out of ideas, does anyone know of some global setting that sits outside the workspace and outside the Indigo installation folder that could be causing this?
I'm running on Win 7 64 bit ultimate, I run the 32 bit version of Indigo because the 64 bit doesn't appear to work with the NetBurner plug-ins. I've also disabled the two Mylyn tasks under General->Startup and Shutdown (they seemed to cause many Permgen memory crashes). This is the same setup I had working flawlessly yesterday.
Update
I also noticed that only 3 of the 4plug-ins are showing up in the Installation Details plug-in pane. The nbeclipse.core_2.6.0.jar is in the eclipse plugin directory but not showing as loaded. So I guess I know now the problem is the plug-in isn't loading but I don't know why or how to get it to load, or what subclipse could have changed that would cause this.
I suspect that the Subclipse installation may have caused an update to some other plugin(s) that it depended on (keep in mind the transitive nature plugin dependency resolution; if you're installing plugin A and it requires a certain version of Plugin B that you don't have, Plugin B will be installed or updated to that version). In doing so, maybe the NetBurner plugin can no longer load because its declared dependencies are no longer met (ie, it depended on an earlier version and does not tolerate a later version).
You can use the OSGi Console to help determine why a plugin is not loading. Here are a couple of references that should help:
http://grep.elasticpath.com/community/techblog/blog/2010/05/27/eclipse-plugins-and-the-osgi-console
http://www.vogella.com/articles/OSGi/article.html#osgiconsole
By the way, you can not just copy plugins into an Eclipse installation and expect them to work. For several versions now, Eclipse has not supported that ability. You must use Help > Install New Software or File > Import > Install > From Existing Installation to install plugins. Ask the vendor if they have an update site to install from; like I said above, simply dropping things into Eclipse's plugins folder is not supported any more, it won't work. Other than the vendor providing an update site, the only other option is to use the dropins folder, as described here.
I have a central GIT repository, so that i can work on the project from different computers.
However when i pull the project on the other computer i get the error "Unbound classpath container: 'GWT SDK [missing]' in project 'Test Project'" (I also get a similar error for GAE).
So my question is: How do i setup my project so the same version of GAE/GWT is used on all computers.
I suspect the problem could be caused by the different versions of GAE and GWT on the machines. For example: GWT (1) is not the same version on the machines as it depends on when you updated GWT.
I ran into this problem too, and solved it by installing the GAE and GWT sdks under specific names, manually. That is, instead of relying on eclipse's software update tools, I downloaded the specific SDK version I wanted from the googlecode sites, and then added them manually to eclipse. This way their names include the numbers, and your git repository can store information about which versions it's using.
I do have to install the sdks manually on each developer machine, which is a drag.
To install an sdk manually:
Download it
Right-click on the sdk container in eclipse (in project explorer, it probably says GWT SDK [missing])
Choose properties
Click configure SDKs
follow the path to install a new sdk
You don't have to set the new sdk as default or anything - your project will pick it up immediately after you install it.
Note to any GPE developers: it'd be nice if the sdks were installed automatically with a version-specific name for the benefit of source control!
You can Change the project's SDK target.
In eclipse go to Marker [it is a tab next on the extreme left of the tabs including Console and Development] --> Left Click problem indication --> Click Quick fixes and choose the option which re-configures the project. This should fix the problem. Note that if your code uses features that changed between SDK versions you will have to make changes.
Combined with Rilev Lark's answer This is a chance to Update your projects or your environments whenever the problem occurs.
In the past I've always downloaded the new version, and then manually reinstalled all of the plugins I use - but this is tedious in the extreme.
Is there a way to upgrade Eclipse "in-place"? How do I do this exactly?
The approach below worked for me, and seems to be the easiest. It's from this eclipse FAQ and slightly modified for clarity:
For upgrading from Eclipse 3.5+ to 3.6+
Help -> Install New Software
Enter the release update site url eg. 'http://download.eclipse.org/releases/indigo' <- if upgrading from 3.5 or 3.6 (Helios) to 3.7 (Indigo)
Click Add
Click Cancel
Help -> Check for Updates
Note: The original URL has changed. (I've left the original link for posterity)
following the NEW FAQ instructions
Also you may have to remove any incompatible updates plugins before proceeding.
(For Example: JBoss Tools has different versions for Helios and Indigo that are incompatible)
Update: I didn't try this when upgrading from 3.x to 4.x (Juno). I just set up a whole new workspace. I think I read somewhere that doing that is the safest approach to upgrading major versions.
As of 3.7 (Indigo), you may export/import install configurations via the
File > Import/Export > Install menu.
This allows you to install a new release of Eclipse, point it at your
existing workspace, and install your plugins from an older installed
copy.
If you always download all plugins manually and then deploy it by copying to dropins folder, then while migrating to newer version, just need to copy that folder to the new eclipse.
And even not all plugins will support newer version of Eclipse so I guess there is no really easy way available to do the migration.
The answer is, there is none. It's pointless to speculate here as to why the Eclipse community chooses not to make one. They haven't.