Now that the new version of eclipse is out should I move to immediately? If my plug-ins work in Galileo will it work in the indigo?
There is no way to know without trying or researching what the particular plugin providers state regarding Indigo compatibility. Many plugins will work just fine. Some will not.
I would recommend starting a separate Indigo install along side your working Galileo install. Then install your plugins into the new install one by one. If everything installs and appears to be working, you can safely transition. If it doesn't, you will know which plugins are incompatible. Maybe a newer version exists or is on the way.
I am planning not to switch before SR2 is available. In the past new Eclipse versions had some minor bugs and I don't see the big advantage of Indigo for my daily work.
It is a risk worth taking. First, create a copy of your eclipse installation and upgrade and see if your plugins are working fine.
If those are working it's good to go Indigo.
All the best with Indigo.
Related
I'm working for a long time with Eclipse Helios 3.6 and have a lot of plugins installed from the Eclipse webpage. Now, I wanted switch to the Eclipse Version Juno 4.2
My question: Can I use the old plugins from my Helios or must I reinstall the plugins ?
I am not too sure, but Eclipse should be backwards compatible. Just add the update site for Eclipse 4.2, run the upgrade and the plugins should continue to work. Sometimes features (that are possibly used by the plugins) are marked as deprecated, but I think they are not removed from Eclipse.
Other than that: You could make a backup (or a simple copy) and try it out to be sure.
After a ubuntu update all my eclipse plugin have disappeared, inclcuding ADT Plugin, Database Plugin, and PHP Plugin. If I install "new" software, eclipse gives my the error "Duplicated Location". Great
Any ideas how to fix this?
Did the Eclipse version get updated? Either way, from my experience the best option is to do a fresh install of Eclipse to make sure there's no cruft sitting around from previous installations (better to eliminate the possibility now then have some bug down the road that may be attributed to a code issue).
I am sure somebody might have come across this scenario.
I have many working sets in my present workspace (Eclipse Helios version). I am trying to migrate the same to Indigo SR2 version.
Simple workspace migration from one version of Eclipse to another also I have not done earlier.
Please let me know how to proceed with the same
Normally, everything should go fine when you install all the plug-ins in Indigo which you have in Helios. Then you just open your workspace with Helios, you are good to go, but of course, a full workspace compilation might be done.
As far as I know, Indigo used to have some problems with Maven support, I don't know if it has been fixed.
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.
I have been searching for a new IDE for a while. I finally decided to try Eclipse, although I am a little discontent with the memory usage, and I really like a lot of aspects about it. There are, as with learning any new IDE, some things that I haven't been able to figure out yet. One of the biggest ones is that it seems like no matter what plugin in I install it doesn't work, or doesn't appear to.
I downloaded Eclipse Galileo just to make sure that I could get plugins working there, since I know Helios is pretty new, and plugins worked in Galileo as expected. Is there something different that you have to do in Helios that I haven't discovered yet or am I missing something?
I have tried installing RSE, Subclipse, and Drupal for Eclipse (I am a Drupal developer). None of these work in Helios, but all work in Galileo.
Any help from Eclipse users would be greatly appreciated!
There's the new marketplace, so rather than using
Help -> Install New Software,
check out
Help -> Eclipse Marketplace.
I've had a similar issue with the m2eclipse plugin, but found installing it through the marketplace worked fine!