From other related posts, the recommended "best practice" is to create a "parallel" installation of Eclipse 3.6 (Helios). But I wish it were that simple ...
On my system, the installation package for 3.5 (Galileo) seems to have distributed the Eclipse system files over many different file-system locations:
/usr/lib/eclipse
/usr/bin/eclipse
/usr/share/
/var/lib/dpkg/info/
/etc/eclipse.ini
~/.eclipse
It's not at all clear to me what a "parallel" installation would look like in this case. Can someone enlighten me?
Would I be better off just deleting everything other than my workspace files that appears to involve Eclipse, and try to do a clean install of Helios?
Thanks.
I, personally, always download the ZIP package of Eclipse from eclipse.org and don't use the system's Eclipse package at all. It just makes everything cleaner. Then, when upgrading, I delete the old Eclipse folder, unzip the new one, and maybe keep options in eclipse.ini. The only difficulty is with the plugins but I keep links to the update sites so it's no big deal to download and install them again.
Related
To upgrade to a new version, the eclipse FAQ suggests to add a new repository and then install available updates. Upgrading to Neon, the corresponding repository is http://download.eclipse.org/releases/neon/.
On this page, it says:
NOTE: Due to structural changes you cannot update from a Mars (or prior) all-in-one package to a Neon version. If interested in the technical details, see bug 332989 and bug 490515.
I still tried to above procedure, but no updates were found. What is the best way to upgrade from Mars to Neon? A complete new installation? How do I preserve my settings?
The note on the repository page is right. Thanks to your report, I edited the FAQ to make it clear that upgrading packages from Mars to Neon is not supported.
Instead you need to to a fresh install for Neon (or later).
I tried to upgrade in the recommended way, by adding the repository links and doing an update, but then I got a lot of conflict messages. I foolishly tried to remove the conflicting software components, until it told me that Eclipse itself was the conflict! I posted my problem to the Eclipse Forums, and was told by a regular with tens of thousands of posts that Neon was so different that I should not even try to upgrade, just create a new installation. When I tried to do that however, I got lots of warnings "That the artifact download is progressing very slowly from ..."
It is not possible to upgrade from Mars (or earlier versions), so a new install is needed.
This can be in parallel with the old install. From the FAQ:
Fresh install
If you prefer not performing an update (for example
because some 3rd-party content isn't ready for the current release of
Eclipse IDE so the update reports conflicts), you can still download a
fresh install of the Eclipse IDE and install it in another location on
your filesystem, and use it together with the previous version.
To do so, download a new build from the Eclipse download Web site
(https://www.eclipse.org/downloads/eclipse-packages/) and run the
installer or unzip the archive in a new directory. We strongly
recommend against installing/unzipping over your existing version of
Eclipse IDE as it may corrupt your installation.
When you start a new version of Eclipse IDE, you can use the same
existing workspace folder that you were using with older version. The
workspace will be migrated to newer version and Eclipse IDE will to
reuse all configuration. The workspace is forward compatible
The exact OS I'm using is RedHat 6.5 Enterprise, 32 bit. I believe Eclipse was installed using yum.
I have tried multiple URLs to try to install an SVN plugin using Eclipse's Help->Install New Software function, including this one: http://subclipse.tigris.org/update_1.10.x, which I found here: http://subclipse.tigris.org/servlets/ProjectProcess?pageID=p4wYuA
Eclipse installed the plugin successfully, but whenever I start Eclipse, the plugin is nowhere to be found. I tried starting Eclipse with the -clean option, and that isn't doing anything.
Therefore, from the site I linked above, I downloaded the .zip file of the plugin from here: http://subclipse.tigris.org/servlets/ProjectDocumentList?folderID=2240. The exact file I downloaded is site-1.8.22.zip.
I had this same problem in the past with Mercurial where installing from Help->Install New Software didn't work, so I downloaded that jar (for some reason there is only one jar for Mercurial but for SVN there are many plus some directories?). I then put that jar in /usr/share/eclipse/dropins/plugins (I had to create the plugins directory). That worked. However, when I put all of the SVN jars in there, SVN is not showing up in Eclipse. I have tried many different combinations of putting only some jars in there, creating folders, etc. Again, I have been using -clean when starting eclipse, and that's not making a difference. I truly think the plugin isn't being put in the right spot because I can move the Mercurial plugin I have installed in and out, and it shows that correctly in Eclipse each time. For reference, the Mercurial jar I'm using is: com.vectrace.MercurialEclipse_2.1.0.201304290948.jar
I also noticed that /etc/eclipse.ini has this line in it, which should say where to look for plugins: -Dorg.eclipse.equinox.p2.reconciler.dropins.directory=/usr/share/eclipse/dropins
So I have some questions:
Where do I put all of these SVN jars and folders that I downloaded?
Why does the Mercurial one only have one jar and the SVN have a whole bunch? I'm just curious why the developers would package these completely differently because maybe this means there's a single SVN jar out there that I could use and just have it work.
I also found a /usr/lib/eclipse folder, and there are also plugin and dropin folders in there. Why are there multiple Eclipse directories for plugins?
I believe I was using the wrong version of java. I downloaded the latest version of Eclipse, and that required me to update my java version in order to run it. I updated to 1.8 (was using 1.6). I think the latest Subclipse plugin requires something at least higher than 1.6. There were no warnings or error messages to let me know about this, so that's why it was difficult to figure out.
Once I started using the new Eclipse and Java 1.8, I was able to easily install and use Subsclipse using Help->Install New Software.
I haven't found one to install Eclipse 4.2 Juno. Default Ubuntu repositories (I'm using Ubuntu 10.04) suggest me the archaic Galileo version. And I found the Eclipse's page on Launchpad which was updated in 2009.
I can, of course, simply download the archive with all the files from http://www.eclipse.org/downloads/, but that's not Debian way, is it? I mean, no automatic updates and other aptitude-managed cool things.
So, is there any repository that maintains the most recent version of Eclipse?
I think it is unlikely that you will find a newer package for Lucid. People tend to create packages for newer versions of Ubuntu.
If it's not possible to upgrade Ubuntu, what you could try is to make your own package but you would still not get automatic upgrades. From a quick look, it looks like that Juno needs some libraries to build that could be newer than the versions you have in your system, so this may end up being quite difficult. It could possibly be the reason why it is not available for Lucid in the first place.
If Juno works in your system, the quick and dirty solution is to first create a temporary folder, e.g. eclipse_3.8.0 and then do the following:
mkdir /path/to/eclipse_3.8.0/DEBIAN
mkdir /path/to/eclipse_3.8.0/opt
tar xzvf eclipse-juno.tar.gz -C /path/to/eclipse_3.8.0/opt
dpkg-deb -b --no-check /path/to/eclipse_3.8.0
This will create a deb package that installs eclipse in /opt/eclipse. You may want to put a control file inside the DEBIAN folder to add a description, dependencies, etc.
If you still want to give building a try, from the official ubuntu launchpad page for eclipse you can download the source files and especially the control files stored in the xxx.debian.tar.gz file. Take a look at the Debian wiki for some tips on how to build. Precise has the Indigo SR2 version and Quantal seems to have Juno.
How can I migrate my eclipse and plugins from my computer to my laptop?
My eclipse has an ADT and Android plugins and I dunno if it works to copy only the eclipse folder.
Just copy the eclipse folder. But some configurations will get lost because they are made per workspace. So you might also want to copy a workspace.
Copying the Eclipse folder should work. Try it.
Having said that, when I'm in the same situation I usually just do a reinstall of Eclipse - it doesn't take long assuming you have a fast network connection and it's a good opportunity to get a clean install with all the latest plugin versions.
We have a custom plug-in. That is, the company where I'm working developed it in house.
I would like to install it as an available plug-in in Eclipse Ganymede. How do I do that?
From what I can figure out, the Eclipse software install only supports installation from Eclipse software update sites.
I went to Help -> Install New Software... -> Add -> Local...
to browse to a folder containing the plug-in. Although the dialog lets me add the directory as an update site, it doesn't work. It expects that directory to be a local Eclipse update site (I think). I get the error
No repository found at file:/G:/TOOLS/...
Next I just copied the plug-in into the plug-in directory under my Eclipse installation. That didn't work either. I also tried copying it into the dropins directory. No dice.
Can anyone enlighten me how to install a plug-in that's not on an "update" site?
Thanks in advance....
Usually an Eclipse plug-in packaged as zip file is install by extracting it into the Eclipse installation directory (or the plugins directory depending on how it is packaged, as it can also extract files in features directory).
Next restart Eclipse with the --clean option.
Did you check the Eclipse error log? Maybe the bundle is failing to deploy for some reason.
Otherwise, create a Feature and Update Site for your plugin as described here. An update site can either be a remote http server (SVN even), or a local directory. The nice thing is that you'll get versioning and the ability to upgrade and uninstall from inside Eclipse. It also makes things easier once your plugin grows into several plugins because they can be bundled together into a single, versioned feature.