Gentlemen (and ladies?), after much ado, I present to you an ebuild for Eclipse SDK 3.5.2 (and Jetty 6.1.24). * Based on eclipse-sdk-3.5.1-r1.ebuild in Portage tree (also written by me). * Uses Eclipse Build 0.5.0 from the Eclipse Linux Tools project. * Builds 100% against system-installed dependencies (no bundled class files, jars, or shared objects). * Supports per-user installation of plugins using P2.
Created attachment 239153 [details] eclipse-3.5.2-ebuilds.tar.bz2
Please only attach plain text files.
Created attachment 239155 [details] www-servers/jetty/metadata.xml
Created attachment 239157 [details] www-servers/jetty/jetty-6.1.24.ebuild
Created attachment 239159 [details] www-servers/jetty/Manifest
Created attachment 239161 [details] dev-util/eclipse-sdk/metadata.xml
Created attachment 239163 [details] dev-util/eclipse-sdk/eclipse-sdk-3.5.2.ebuild
Created attachment 239165 [details] dev-util/eclipse-sdk/Manifest
(In reply to comment #5) > Created an attachment (id=239159) [details] > www-servers/jetty/Manifest > The developers can generate the Manifests when they work with ebuilds so you don't need to upload them to bugzilla. (In reply to comment #4) > Created an attachment (id=239157) [details] > www-servers/jetty/jetty-6.1.24.ebuild > You should open a dependency bug for jetty to only handle one issue per bug. (In reply to comment #6) > Created an attachment (id=239161) [details] > dev-util/eclipse-sdk/metadata.xml > This is a copy of the existing file so there's no use in uploading it to bugzilla.
(In reply to comment #9) > The developers can generate the Manifests when they work with ebuilds so you > don't need to upload them to bugzilla. I attached the Manifests because they contain checksums of the distribution tarballs. Without them, there is no way for anyone else to know whether they retrieved the same tarball that I tested against. (Yes, the file should not change, but I've seen it happen on more than one occasion, and it confuses people greatly until it's discovered that there are two different versions of the file with the same name.) > You should open a dependency bug for jetty to only handle one issue per bug. Created: http://bugs.gentoo.org/show_bug.cgi?id=328747
Although Eclipse itself runs fine, [EJ]Git does not seem to work anymore after updating to the ebuild posted here. Neither can I commit changes nor can I fetch updates or do anything git related. I also can't even share a project with git because there's no selection screen for cvs/git anymore. Only after downgrading to portage's 3.5.1-r1 and using a backup's ~/.eclipse folder I have all my beloved git features back again. Is there something I'm missing or debug info I can supply you with to fix this?
(In reply to comment #11) > Although Eclipse itself runs fine, [EJ]Git does not seem to work anymore after > updating to the ebuild posted here. Neither can I commit changes nor can I > fetch updates or do anything git related. I also can't even share a project > with git because there's no selection screen for cvs/git anymore. > Only after downgrading to portage's 3.5.1-r1 and using a backup's ~/.eclipse > folder I have all my beloved git features back again. > > Is there something I'm missing or debug info I can supply you with to fix this? I lost all of my plugins when I upgraded to Eclipse 3.5.2 using this ebuild. Reinstalling them through the user interface inside Eclipse didn't bring them back. I had to blow away my ~/.eclipse directory and then reinstall them. All the important settings are saved in your workspace dir anyway, so there's nothing critical lost when you delete ~/.eclipse (aside from local edit history, I think).
Thank you for the tip (and the ebuild, of course), that did the trick. You should consider adding a little note about this in the ebuild. I can't remember needing anything like this when updating from 3.4 to 3.5 (then again, I don't think I had any plugins installed at that time) Will this also happen with Eclipse 3.6 (bug 325271)?
which herd takes care of eclipse-sdk? java oder dev-tools? #307831 and this bug seem to want the same thing.
isn't this technically a duplicate of #307831 ? either one of them should be closed, also i wonder if developers going to put 3.5.2 anyway or just skip right to 3.6 #325271
*** Bug 307831 has been marked as a duplicate of this bug. ***
eclipse 3.7 is out ... Gentoo, what are you doing here!
(In reply to comment #17) > eclipse 3.7 is out ... Gentoo, what are you doing here! *cough* https://bugs.gentoo.org/show_bug.cgi?id=325271#c68
4.3 is out...
*** This bug has been marked as a duplicate of bug 325271 ***
