After a couple of hours debuging and diffing with a manual installation I found out why the current eclipse 2.1 ebuilds (both SDK and normal) break the update manager feature. The eclipse install location (/opt/eclipse) needs to have a .eclipseproduct file which is in the .zip package but doesn't get copied by the ebuild script. Reproducible: Always Steps to Reproduce: 1. emerge eclipse 2. start eclipse and select Software Update -> Update Manager under the Help menu. 3. Look in Installation Configuration view under Eclipse Platform: the file:/opt/eclipse location has a type 'User', but it should be 'Product' 4. Try to install a third party plugin 5. The target locaction selection will always be empty 6. Installation not possible Actual Results: installation of third party plugin did not work Expected Results: plugin should be installed
we have never done any eclipse stuff, so please reassign to the maintainer
I can confirm this bug and I'm interested in its correction... it's nasty having to switch to windows just to get the desired plugins...
Bug still going strong. It would be nice if the binary ebuild was updated to the most current stable release (2.1.2) as a temporary fix.
I tried manually copying the .eclipseproduct file from the unpacked work directory up to /opt/eclipse, but no joy. [In my case, it's failing trying to install an ANT upgrade, but whatever] Is this a permissions issue? With /opt/eclipse being owned by root, and me running eclipse as joe user... AfC
After further investigation I have determined this is not gentoo specific nor the ebuilds fault. I have submitted a bug report to the eclipse dev team that contains all the relevant information here: http://www.eclipse.org (click on the "bugs" link in the left menuboard) bug #54745 Add additional information to my report if you can.
Ok - silly workaround time. I'm on a workstation (as opposed to a shared development box with lots of people on it, so could get away with this): As root: 1. copied .eclipseproduct in from PORTAGE_TMPDIR/eclipse.../work/eclipse/ up to /opt/eclipse 2. chown -R andrew:users /opt/eclipse While there may be deeper issues, this allowed me to enable eclipse to get on with unpacking, and overwriting things in the distribution directory using it's built in Update Manager when running as my normal user id. As I said, a HUGE cludge, but I'm working 2.1.2 now, which seems like progress (although ultimately resulted in double downloads since almost everything got updated) I would certainly appreciate some guidence of how I should deploy / manage eclipse in a Gentoo context, but reading the related bugs I'm not sure anyone has an answer to that just yet. It WOULD be cool if we could use ebuilds for plugins (like using Perl ebuilds instead of going to CPAN direct) but that's a lot of work for the dev team and I appreciate that - especially when Eclipse has a built in update manager - there has to be a good reason... AfC Sydney
The update manager in dev-util/eclipse-sdk-2.1.3-r2 works. There are currently a few caveats: 1) When asked about "Install Location", you must "Add.." a location where you have write-access (say $HOME/.eclipse-plugins for a per-user installation or /usr/local/share/eclipse-plugins-2 for a system-wide installation, provided your user has write-access to that dir). 2) The plugins will be installed on a per-workspace basis. If you create a new workspace, you will need to install the plugins again. I am working on a clean workaround for the latter problem, so you can select whether it's a workspace-only or user-only or system-wide plugin you're about to install. Also, I guess it would be nice to be able to change the role of a plugin, say, "promote" a workspace-only plugin to a user-only plugin.
