released today? recently at least.
(In reply to comment #0) > released today? recently at least. > Please do not file 0'day requests. When the maintainer doesn't react within a week, it's early enough to do so.
well, considering that no work has been done in months on the previous version bump request for eclipse, I assumed the maintainer was mia or otherwise preocupied. Plus I was initially wrong. looks like the release was on the 17th. 9 days ago.
It was released officially on June 25th (not 17th). I (actual maintainer of Eclipse) have been devaway for quite a while. However if my current workload allows, I will try to package Eclipse 3.4. If I don't do it someone else from the Java team may work on it - so hopefully Eclipse 3.4 will be in Portage soon (I certainly hope it'll be faster than Eclipse 3.3 that I have not even be able to stabilize).
(In reply to comment #3) > It was released officially on June 25th (not 17th). I (actual maintainer of > Eclipse) have been devaway for quite a while. However if my current workload > allows, I will try to package Eclipse 3.4. If I don't do it someone else from > the Java team may work on it - so hopefully Eclipse 3.4 will be in Portage soon > (I certainly hope it'll be faster than Eclipse 3.3 that I have not even be able > to stabilize). > I too have not even been able to upgrade to 3.3 (it crashes alot). Please bump asap
(In reply to comment #4) > I too have not even been able to upgrade to 3.3 (it crashes alot). If you're experiencing the problem where Eclipse 3.3 hangs for a few seconds and then disappears, you may have the same problem I had, which I solved by creating a file ~/.gentoo/eclipserc containing: ECLIPSE_MAX_PERMSIZE=128M The default MaxPermSize of the JDK (64 MB) is insufficient to run Eclipse reliably. (I'm using Sun JDK 1.6 on x86_64.) Before I discovered this fix, Eclipse would crash on me several times a day. With the increased MaxPermSize, I have used a single instance of Eclipse for over a week with no problems.
Also set in /etc/eclipserc with descriptions. Not sure why this isn't enabled by default. (In reply to comment #5) > (In reply to comment #4) > > I too have not even been able to upgrade to 3.3 (it crashes alot). > > If you're experiencing the problem where Eclipse 3.3 hangs for a few seconds > and then disappears, you may have the same problem I had, which I solved by > creating a file ~/.gentoo/eclipserc containing: > ECLIPSE_MAX_PERMSIZE=128M > > The default MaxPermSize of the JDK (64 MB) is insufficient to run Eclipse > reliably. (I'm using Sun JDK 1.6 on x86_64.) Before I discovered this fix, > Eclipse would crash on me several times a day. With the increased MaxPermSize, > I have used a single instance of Eclipse for over a week with no problems. >
Is this in an overlay somewhere I am getting real sick and tired of 3.3 crashing randomly for no reason about a binary lib error.
I've created an eclipse overlay and so far it has dev-util/eclipse-sdk-bin-3.4.ebuild. The ebuild is very simple and basically just repackages the official eclipse 'classic' ganymede release from eclipse.org. If you're using layman, then layman -o http://virtb.visibleassets.com:2080/layman.conf -a eclipse Alternatively, if you would prefer to install from a tbz2 package, then echo "dev-portage/eclipse-sdk-bin" >> /etc/portage/package.keywords PORTAGE_BINHOST="http://virtb.visibleassets.com:2080/geeentoo/packages/All" \ FEATURES="getbinpkg" \ emerge -Kav1 =dev-util/eclipse-sdk-bin-3.4 At the moment there are no 'major' bugs with Ganymede, but I really dislike the pervasive 'show view as fast view' button that will not go away and steals visual real estate. However, that really only effects users with small screens I guess. For that reason, I'm switching back to eclipse-3.3.1.1 though.
The java overlay[1] has an ebuild for eclipse 3.4. It has a major issue in installing though. It forgets to install the "p2" directory. This is decribed in comment #11 in [2]. If one gets around fixing that eclipse should work flawless. [1] http://overlays.gentoo.org/proj/java/ [2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=238910
Ebuild for version 3.4 just commited to main tree, please test and report.
addons cannot be installed. that is possible in 3.3.1.1.-r2. please fix.
Read the installatiomn message. Addons can be installed, you must enable classic Update manager.
Eclipse for me is failing to start with this in ~/workspace/.metadata/.log: java.version=1.5.0_15 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US Framework arguments: Command-line arguments: -os linux -ws gtk -arch x86 !ENTRY org.eclipse.osgi 4 0 2008-08-05 10:35:57.171 !MESSAGE Application error !STACK 1 java.lang.UnsatisfiedLinkError: no swt-gtk-3448 or swt-gtk in swt.library.path, java.library.path or the jar file at org.eclipse.swt.internal.Library.loadLibrary(Unknown Source) at org.eclipse.swt.internal.Library.loadLibrary(Unknown Source) at org.eclipse.swt.internal.C.<clinit>(Unknown Source) at org.eclipse.swt.internal.Converter.wcsToMbcs(Unknown Source) at org.eclipse.swt.internal.Converter.wcsToMbcs(Unknown Source) at org.eclipse.swt.widgets.Display.<clinit>(Unknown Source) at org.eclipse.ui.internal.Workbench.createDisplay(Workbench.java:509) at org.eclipse.ui.PlatformUI.createDisplay(PlatformUI.java:161) at org.eclipse.ui.internal.ide.application.IDEApplication.createDisplay(IDEApplication.java:143) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:88) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504) at org.eclipse.equinox.launcher.Main.run(Main.java:1236) at org.eclipse.equinox.launcher.Main.main(Main.java:1212) !ENTRY org.eclipse.osgi 2 0 2008-08-05 10:35:57.333 !MESSAGE The following is a complete list of bundles which are not resolved, see the prior log entry for the root cause if it exists: !SUBENTRY 1 org.eclipse.osgi 2 0 2008-08-05 10:35:57.333 !MESSAGE Bundle update@plugins/org.eclipse.jdt.compiler.apt_1.0.100.v20080513-1235.jar [85] was not resolved. !SUBENTRY 2 org.eclipse.jdt.compiler.apt 2 0 2008-08-05 10:35:57.333 !MESSAGE Missing imported package org.eclipse.jdt.internal.compiler.tool_0.0.0. !SUBENTRY 1 org.eclipse.osgi 2 0 2008-08-05 10:35:57.333 !MESSAGE Bundle update@plugins/org.eclipse.jdt.compiler.tool_1.0.100.v_874.jar [194] was not resolved. !SUBENTRY 2 org.eclipse.jdt.compiler.tool 2 0 2008-08-05 10:35:57.333 !MESSAGE Missing Constraint: Bundle-RequiredExecutionEnvironment: JavaSE-1.6 !SUBENTRY 1 org.eclipse.osgi 2 0 2008-08-05 10:35:57.333 !MESSAGE Bundle update@plugins/org.eclipse.jdt.apt.pluggable.core_1.0.100.v20080407-1345.jar [260] was not resolved. !SUBENTRY 2 org.eclipse.jdt.apt.pluggable.core 2 0 2008-08-05 10:35:57.333 !MESSAGE Missing imported package org.eclipse.jdt.internal.compiler.tool_0.0.0. !SUBENTRY 2 org.eclipse.jdt.apt.pluggable.core 2 0 2008-08-05 10:35:57.333 !MESSAGE Missing imported package org.eclipse.jdt.internal.compiler.apt.dispatch_0.0.0. !SUBENTRY 2 org.eclipse.jdt.apt.pluggable.core 2 0 2008-08-05 10:35:57.333 !MESSAGE Missing imported package org.eclipse.jdt.internal.compiler.apt.model_0.0.0. !SUBENTRY 2 org.eclipse.jdt.apt.pluggable.core 2 0 2008-08-05 10:35:57.352 !MESSAGE Missing imported package org.eclipse.jdt.internal.compiler.apt.util_0.0.0. I've double-checked and swt-3.4 is installed. It seems to include the library mentioned in the error. I've tried re-emerging swt-3.4 already, and I've done a revdep-rebuild. Anyone else see this, or have suggestions? BTW, thanks for getting this ebuild out!
Have successfully installed dev-util/eclipse-sdk-3.4-r2 on ~amd64, thanks! OTOH, there is a 3.4-stopper: https://bugs.eclipse.org/bugs/show_bug.cgi?id=239785 Are there a chance our brave Gentoo-Java team will eliminate the issue? Unfortunately, Eclipse team keeps silent :-)
eclipse-sdk-3.4-r2 crashes with SIGSEGV. # # An unexpected error has been detected by Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00007f4097ed025a, pid=2363, tid=1082341712 # # Java VM: Java HotSpot(TM) 64-Bit Server VM (10.0-b23 mixed mode linux-amd64) # Problematic frame: # V [libjvm.so+0x1f125a] # [...] --------------- T H R E A D --------------- Current thread (0x0000000042128800): JavaThread "CompilerThread0" daemon [_thread_in_native, id=2377, stack(0x0000000040733000,0x 0000000040834000)] [...] Current CompileTask: C2:695 org.eclipse.core.internal.dtree.DataTreeNode.forwardDeltaWith([Lorg/eclipse/core/internal/dtree/AbstractDataTreeNode;[Lorg/eclipse/core/internal/dtree/AbstractDataTreeNode;Lorg/eclipse/core/internal/dtree/IComparator;)[Lorg/eclipse/core/internal/dtree/AbstractDataTreeNode; (469 bytes) And also this, which is different: # # An unexpected error has been detected by Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00007f8431f2625a, pid=2660, tid=1090296144 # # Java VM: Java HotSpot(TM) 64-Bit Server VM (10.0-b23 mixed mode linux-amd64) # Problematic frame: # V [libjvm.so+0x1f125a] # [...] --------------- T H R E A D --------------- Current thread (0x00007f8408001000): JavaThread "CompilerThread0" daemon [_thread_in_native, id=2670, stack(0x0000000040ec9000,0x0000000040fca000)] [...] Current CompileTask: C2:1134 org.eclipse.jdt.internal.compiler.lookup.ParameterizedMethodBinding.<init>(Lorg/eclipse/jdt/internal/compiler/lookup/ParameterizedTypeBinding;Lorg/eclipse/jdt/internal/compiler/lookup/MethodBinding;)V (596 bytes)
(In reply to comment #13) Here, the same error occurs, content of ~/workspace/.metadata/.log: !SESSION 2008-08-07 15:01:49.715 ----------------------------------------------- eclipse.buildId=I20080617-2000 java.version=1.5.0_16 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=de_DE Framework arguments: Command-line arguments: -os linux -ws gtk -arch x86 !ENTRY org.eclipse.osgi 4 0 2008-08-07 15:02:05.672 !MESSAGE Application error !STACK 1 java.lang.UnsatisfiedLinkError: no swt-gtk-3448 or swt-gtk in swt.library.path, java.library.path or the jar file at org.eclipse.swt.internal.Library.loadLibrary(Unknown Source) at org.eclipse.swt.internal.Library.loadLibrary(Unknown Source) at org.eclipse.swt.internal.C.<clinit>(Unknown Source) at org.eclipse.swt.internal.Converter.wcsToMbcs(Unknown Source) at org.eclipse.swt.internal.Converter.wcsToMbcs(Unknown Source) at org.eclipse.swt.widgets.Display.<clinit>(Unknown Source) at org.eclipse.ui.internal.Workbench.createDisplay(Workbench.java:509) at org.eclipse.ui.PlatformUI.createDisplay(PlatformUI.java:161) at org.eclipse.ui.internal.ide.application.IDEApplication.createDisplay(IDEApplication.java:143) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:88) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504) at org.eclipse.equinox.launcher.Main.run(Main.java:1236) at org.eclipse.equinox.launcher.Main.main(Main.java:1212) I remerged swt and eclipse-sdk, but the error stays reproducable. Even giving -Djava.library.path="/usr/share/swt-3.4/lib;/usr/lib" at the command line did not change anything. Eclipse 3.3 worked fine at this machine. # emerge --info Portage 2.1.4.4 (default/linux/x86/2008.0/desktop, gcc-4.1.2, glibc-2.6.1-r0, 2.6.25-gentoo-r7 i686) ================================================================= System uname: 2.6.25-gentoo-r7 i686 Pentium III (Coppermine) Timestamp of tree: Wed, 06 Aug 2008 17:45:01 +0000 distcc 2.18.3 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled] app-shells/bash: 3.2_p33 dev-java/java-config: 1.3.7, 2.1.6 dev-lang/python: 2.5.2-r7 sys-apps/baselayout: 1.12.11.1 sys-apps/sandbox: 1.2.18.1-r2 sys-devel/autoconf: 2.13, 2.61-r2 sys-devel/automake: 1.5, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10.1 sys-devel/binutils: 2.18-r3 sys-devel/gcc-config: 1.4.0-r4 sys-devel/libtool: 1.5.26 virtual/os-headers: 2.6.25-r4 ACCEPT_KEYWORDS="x86" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -march=pentium3 -mtune=pentium3 -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/config" CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/fonts/fonts.conf /etc/gconf /etc/php/apache2-php5/ext-active/ /etc/php/cgi-php5/ext-active/ /etc/php/cli-php5/ext-active/ /etc/revdep-rebuild /etc/splash /etc/terminfo /etc/texmf/web2c /etc/udev/rules.d" CXXFLAGS="-O2 -march=pentium3 -mtune=pentium3 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="distcc distlocks metadata-transfer sandbox sfperms strict unmerge-orphans userfetch" GENTOO_MIRRORS="http://mirrors.sec.informatik.tu-darmstadt.de/gentoo/ ftp://ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/ ftp://ftp.gentoo.mesh-solutions.com/gentoo/ " LANG="de_DE@euro" LC_ALL="de_DE.UTF-8" LDFLAGS="-Wl,-O1" LINGUAS="de en" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="X a52 aac aalib acpi aim alsa arts asf audiofile bash-completion berkdb branding bzip2 cairo cddb cdparanoia cdr cli cracklib crypt css cups dbus divx doc dri dvd dvdr dvdread eds emboss encode esd evo examples exif fam fbcon fbsplash ffmpeg firefox flac fortran ftp gd gdbm gif gimpprint glitz gmedia gnutls gpm graphviz gstreamer gtk gtk2 gtkhtml hal iconv icq id3tag imagemagick imap imlib isdnlog jabber java jpeg kde latex ldap libcaca libnotify logitech-mouse logrotate mad midi mikmod mmx mng motif mozdevelop mozilla mp3 mpeg msn mudflap musicbrainz ncurses nls nptlonly nsplugin numeric offensive ogg oggvorbis opengl openmp oscar oss pam pcre pdf perl png ppds pppd python qt3 qt3support qt4 quicktime readline real realmedia reflection samba sdl session spell spl sqlite sse ssl startup-notification svg sysfs tcl tcltk tcpd tetex tiff tk truetype unicode usb vcd videos vim-syntax vorbis win32codecs wmf wmp x86 xcomposite xine xml xorg xscreensaver xulrunner xv xvid zeroconf zlib" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1 emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mmap_emul mulaw multi null plug rate route share shm softvol" APACHE2_MODULES="actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" ELIBC="glibc" INPUT_DEVICES="keyboard mouse" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LINGUAS="de en" USERLAND="GNU" VIDEO_CARDS="nvidia" Unset: CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS
(In reply to comment #13) > Eclipse for me is failing to start with this in ~/workspace/.metadata/.log: > > java.version=1.5.0_15 > java.vendor=Sun Microsystems Inc. > BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US > Framework arguments: > Command-line arguments: -os linux -ws gtk -arch x86 > (...) I had the same problem on my laptop but not on by dev machine at work. Changing my java JVM from 1.5 to 1.6 (with java-config-2) seems to solve the problem .
(In reply to comment #13) > Eclipse for me is failing to start with this in ~/workspace/.metadata/.log: > > java.version=1.5.0_15 > java.vendor=Sun Microsystems Inc. > BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US > Framework arguments: > Command-line arguments: -os linux -ws gtk -arch x86 > > !ENTRY org.eclipse.osgi 4 0 2008-08-05 10:35:57.171 > !MESSAGE Application error > !STACK 1 > java.lang.UnsatisfiedLinkError: no swt-gtk-3448 or swt-gtk in swt.library.path, Next code helps me to run eclipse after the same problem: export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/lib
I have committed a much-improved ebuild (-r3) to java-overlay. The P2 Update Manager works in this version and I have also committed the JRE 1.5 fix.
(In reply to comment #19) > I have committed a much-improved ebuild (-r3) to java-overlay. The P2 Update > Manager works in this version and I have also committed the JRE 1.5 fix. > Thanks! Unfortunately, have got the error shown below. I have not seamonkey at all, and swt is installed with xulrunner flag (and without seamonkey flag). Must I supply some additional info? -------------------------- Unhandled event loop exception No more handles [MOZILLA_FIVE_HOME='/opt/seamonkey'] (java.lang.UnsatisfiedLinkError: no swt-mozilla-gtk-3448 or swt-mozilla-gtk in swt.library.path, java.library.path or the jar file)
I see the problem here. When Elvanor bumped swt in Portage, he forgot to remove it from java-overlay. The version in java-overlay doesn't register the MOZILLA_FIVE_HOME variable, which is needed in order for this to work. I guess I didn't notice because I have Firefox installed, which is used by default. Update your copy of java-overlay, remerge swt and you should be good to go.
(In reply to comment #21) > I see the problem here. When Elvanor bumped swt in Portage, he forgot to remove > it from java-overlay. The version in java-overlay doesn't register the > MOZILLA_FIVE_HOME variable, which is needed in order for this to work. I guess > I didn't notice because I have Firefox installed, which is used by default. > Update your copy of java-overlay, remerge swt and you should be good to go. > James, thanks! - the problem is fixed for me.
Hmm anyone else please hold off on building mine for the moment. I've realised that the way I've unbundled the JARs doesn't quite work right. Unfortunately I didn't realise until I tried to build a plugin from source. Working on a solution now.
Okay I've fixed that now in r4. (-:
I played around a bit with r4. The update manager is now showing up but is not working flawless: * Ganymed update site (http://download.eclipse.org/releases/ganymede) is missing. * Adding the m2eclipse update site (http://m2eclipse.sonatype.org/update/) adds 4 entiries (http://m2eclipse.sonatype.org/update/, http://m2eclipse.codehaus.org/update/, http://m2eclipse.codehaus.org/ and some russian site) * Installing extensions does not cause them to get enabled. I installed m2eclipse and no trace of it is visible (except the P2 update manager says it was installed). Same goes for using the old update manager. I guess ~/.eclipse/org.eclipse.platform_3.4.0_272132067/ is not in the search path? * Installing ajdt (http://download.eclipse.org/tools/ajdt/34/dev/update) fails because it tells me it can't find it's reverences to aspectj. All of this works when downloading the amd64 binary from eclipse. Guess the P2 needs some more love :-/
Okay, I haven't looked into this too deeply yet but I've got some thoughts on it. I suspect the Ganymede update site is missing because this is an "unofficial" build so to speak. There's probably a way to add it at build time and I'll look into that. I notice that if I try to install AJDT before adding the Ganymede update site, it complains that it cannot find Mylyn. After adding the site, it doesn't complain about that anymore. It does still complain about another missing plugin though but I found that if I used AJDT's "temp" update site, it worked. This may be a problem on their end as http://dev.eclipse.org/mhonarc/lists/ajdt-dev/msg01122.html suggests. M2 seems to complain about Subclipse not being available. I didn't think that would be available in the "default" list of update sites but I'll check it out.
When I try to emerge eclipse with use flags java6 and source, the build fails : If I remove source flag, it builds (it does not work well however, see comment #25 : Installing extensions does not cause them to get enabled) [echo] Assembling... BUILD FAILED /var/tmp/paludis/dev-util-eclipse-sdk-3.4-r4/work/build.xml:127: The following error occurred while executing this line: /var/tmp/paludis/dev-util-eclipse-sdk-3.4-r4/work/package.org.eclipse.sdk.linux.gtk.x86_64.xml:105: srcdir /var/tmp/paludis/dev-util-eclipse-sdk-3.4-r4/work/plugins/javax.servlet.jsp.source_2.0.0.v200806031607 does not exist! Total time: 7 minutes 24 seconds !!! ERROR in dev-util/eclipse-sdk-3.4-r4: !!! In eant at line 1482 !!! eant failed !!! Call stack: !!! * eant (/var/tmp/paludis/dev-util-eclipse-sdk-3.4-r4/temp/loadsaveenv:1482) !!! * src_compile (/var/tmp/paludis/dev-util-eclipse-sdk-3.4-r4/temp/loadsaveenv:5516) !!! * ebuild_f_compile (/usr/libexec/paludis/1/src_compile.bash:49) !!! * ebuild_main (/usr/libexec/paludis/ebuild.bash:463) !!! * main (/usr/libexec/paludis/ebuild.bash:478)
With latest eclipse-sdk-3.4-r4 from java-overlay I'm able to reproduce Gentoo bug #214785 It is reproducible every time I point mouse to some Java method or class, when javadoc tooltip is to be shown.
Sorry for the lack of updates on this. Paid work takes priority. Andrey, have you tried remerging swt?
(In reply to comment #29) > Sorry for the lack of updates on this. Paid work takes priority. Andrey, have > you tried remerging swt? > I totally understand your position about paid work. Yes, I tried reemerging swt, no luck thought. I wonder if someone else could reproduce such behavior. Maybe it is a problem with my concrete installation for some reason.
(In reply to comment #28) > With latest eclipse-sdk-3.4-r4 from java-overlay I'm able to reproduce Gentoo > bug #214785 It is reproducible every time I point mouse to some Java method or > class, when javadoc tooltip is to be shown. > Sorry, it seems that the problem is in MyEclipse extensions. I've tried uninstalling them and the bug has gone.
Thanks for letting us know. I've fixed the issue in comment #27 but I'm going to try and fix the other issue before I commit anything. 3.4.1 also came out a few days ago so I've started moving up to that version.
I've just committed 3.4.1. I was actually unable to reproduce the update manager problem entirely. I grabbed the 3.4.1 amd64 binary tarball and ran that. I found that the Ganymede update site was not present by default on this version either. Trying to install M2 first resulted in the same dependency errors. After adding the Ganymede update site, it installed and run just fine. I then did exactly the same thing with my 3.4.1 ebuild and got exactly the same results. So please try this version and let me know if it works for you. If it doesn't, try starting with a clean configuration.
Aah wait a second. When I tried the binary tarball, I made it read-only for the user because Eclipse operates slightly differently when it is writable. It just occurred to me that the update site may show up if I make it writable. Sure enough, there it is. I'll try and find out why there's a difference here but it sounds like an upstream bug to me.
Turns out it is an upstream bug. I've filed a report. https://bugs.eclipse.org/bugs/show_bug.cgi?id=249133
Has anyone else noticed that the Classic Update no longer works in dev-util/eclipse-sdk-3.4.1 of java-overlay? With a clean ~/.eclipse, I tried installing Subclipse through Classic Update, and though it downloaded, installed, and restarted Eclipse, the plugin did not load. When I went to Manage Configuration, I saw that the extension dir inside ~/.eclipse was not in the list. Anyway, the new update interface seems to work fine now, so no big deal.
(In reply to comment #18) The same problem here (no swt-gtk-3448 or swt-gtk). I have mixed "eclipse-sdk-3.4-r2" with "eclipse-ecj-3.4.1" and "ant-eclipse-ecj-3.4.1". Also I have had installed this side by side with "eclipse 3.2.1-r2". -Cleaning workspace, eclipseworkspace and .eclipse don't fix the problem. -Update overlay (layman -S)and reinstall swt don't fix the problem. Now I have uninstalled all versions and reinstall complete "environment 3.4.1" without "java6" ... and this have started. Now I'm will play something arround.
Created attachment 188403 [details] ebuilds for Eclipse SDK 3.4.2 and dependencies While we wait for an "official" Eclipse 3.4.2 ebuild to hit the tree, here are some ebuilds for Eclipse 3.4.2 and its dependencies. I spent about 20 hours creating and refining the eclipse-sdk-3.4.2.ebuild, so it is thoroughly debugged and tested. Additionally, I have been using the resulting Eclipse 3.4.2 application daily for a few weeks now with no problems. Tested on amd64, but x86 probably will work, too. Don't know about other platforms. Note, there are also ebuilds in this tarball for Eclipse 3.5M6, but I haven't gotten it to work yet. It compiles but won't start. If anyone could figure it out, please let me know.
(In reply to comment #38) > ebuilds for Eclipse SDK 3.4.2 and dependencies > Can anyone add this to the java overlay?
(In reply to comment #39) > Can anyone add this to the java overlay? As far as I can tell, Chewi and Elvanor on #gentoo-java are responsible for the Eclipse SDK ebuild. I submitted my eclipse-sdk-3.4.2 ebuild to Chewi a couple of months ago, and his response was that he would try to take a look at it but was busy and could not guarantee when he'd get around to it. He must be VERY busy or else doesn't care about the Eclipse ebuild under his care.
I was gonna say that sounds a little harsh but given how long it's taken me to reply to this, it's justified. I do care but I have indeed been very busy as the lead developer for a new commercial site. This is why I've resisted the temptation to become a Gentoo dev and prefer to work from the sidelines. Matt's ebuild was cleaner than mine but I felt that some of these cleanups were things that should probably be dealt with by Gentoo's javatoolkit. It's there to deal with ant build files, JAR manifests and the like. What's ultimately stopped either of our ebuilds from going into the tree is the outstanding Eclipse bug that prevents update sites from being propagated down to the user preferences. I did give the bug report a poke not so long ago but the response was basically "we may fix this one day but for now, suck it up." I'm personally not that bothered about it but some of the posters on this bug report appear to be. Our ebuilds may also become obsolete because there is an ongoing project to make building Eclipse on Linux easier. It very recently saw its first preview release. It doesn't support the unbundling of JARs yet but that is planned. I'd much rather use the official (and probably much easier) method than our unsupported and downright messy one.
Kim Moir at IBM has responded to my bug report https://bugs.eclipse.org/bugs/show_bug.cgi?id=271953 and is in the process of creating a new Eclipse SDK source build process that reflects the process currently used to produce the binary packages ("checking out the source, compiling it, generating the metadata, running the p2 publisher, publishing the bundles to a repo and then running the p2 director to assemble the bits from the repo").
Interesting. I wonder if that's the same project as the Linux one or a different one. Someone posted a very similar message to yours on the linuxtools-dev mailing list. The guy was pointed to the Linux project. http://dev.eclipse.org/mhonarc/lists/linuxtools-dev/msg00139.html
*** Bug 238952 has been marked as a duplicate of this bug. ***
(In reply to comment #38) I can't compile eclipse 3.4.2, because I have error like this: ... @dot: [mkdir] Created dir: /var/tmp/portage/dev-util/eclipse-sdk-3.4.2/work/plugins/org.eclipse.jdt.apt.pluggable.core/temp.folder/@dot.bin [javac] Compiling 14 source files to /var/tmp/portage/dev-util/eclipse-sdk-3.4.2/work/plugins/org.eclipse.jdt.apt.pluggable.core/temp.folder/@dot.bin [copy] Copying 14 files to /var/tmp/portage/dev-util/eclipse-sdk-3.4.2/work/plugins/org.eclipse.jdt.apt.pluggable.core/@dot [delete] Deleting directory /var/tmp/portage/dev-util/eclipse-sdk-3.4.2/work/plugins/org.eclipse.jdt.apt.pluggable.core/temp.folder/@dot.bin properties: init: build.jars: properties: init: @dot: [mkdir] Created dir: /var/tmp/portage/dev-util/eclipse-sdk-3.4.2/work/plugins/org.eclipse.jdt.ui/temp.folder/@dot.bin [javac] Compiling 2027 source files to /var/tmp/portage/dev-util/eclipse-sdk-3.4.2/work/plugins/org.eclipse.jdt.ui/temp.folder/@dot.bin BUILD FAILED /var/tmp/portage/dev-util/eclipse-sdk-3.4.2/work/build.xml:68: The following error occurred while executing this line: /var/tmp/portage/dev-util/eclipse-sdk-3.4.2/work/build.xml:8: The following error occurred while executing this line: /var/tmp/portage/dev-util/eclipse-sdk-3.4.2/work/features/org.eclipse.sdk/build.xml:34: The following error occurred while executing this line: /var/tmp/portage/dev-util/eclipse-sdk-3.4.2/work/features/org.eclipse.sdk/build.xml:19: The following error occurred while executing this line: /var/tmp/portage/dev-util/eclipse-sdk-3.4.2/work/features/org.eclipse.jdt/build.xml:109: The following error occurred while executing this line: /var/tmp/portage/dev-util/eclipse-sdk-3.4.2/work/features/org.eclipse.jdt/build.xml:65: The following error occurred while executing this line: /var/tmp/portage/dev-util/eclipse-sdk-3.4.2/work/plugins/org.eclipse.jdt.ui/build.xml:418: The following error occurred while executing this line: /var/tmp/portage/dev-util/eclipse-sdk-3.4.2/work/plugins/org.eclipse.jdt.ui/build.xml:342: java.lang.reflect.InvocationTargetException Total time: 4 minutes 58 seconds emerge --info - http://wklej.to/pjhJ I have no idea why...
(In reply to comment #45) > I can't compile eclipse 3.4.2, because I have error like this: > ... > I have no idea why... My guess would be that you ran out of heap space, the Eclipse Compiler threw an OutOfMemoryError, and Ant caught it as an InvocationTargetException. It's disappointing that Ant doesn't print the chained cause of the ITE, so we can't know for sure. The JVM seems to employ some voodoo for determining its default heap parameters, most probably based on your total and free amounts of system memory. How much do you have? Could you try running the ebuild from a text-mode console without X or any other applications running?
(In reply to comment #46) > My guess would be that you ran out of heap space, the Eclipse Compiler threw an > OutOfMemoryError, and Ant caught it as an InvocationTargetException. It's > disappointing that Ant doesn't print the chained cause of the ITE, so we can't > know for sure. You were right, because when I tried to compile eclipse in verbose mode (add '-v' argument to ant) it showed me this exception - OutOfMemoryError. (part of verbose log - http://wklej.to/u90q). > The JVM seems to employ some voodoo for determining its default heap > parameters, most probably based on your total and free amounts of system > memory. How much do you have? Could you try running the ebuild from a > text-mode console without X or any other applications running? I have 1 GB RAM and 1,5 GB. I have solved this problem by adding ANT_OPTS="-Xmx512M" before 'ant insertBuildId compile' (it was in ebuild for previous version) and it worked. You could add it to ebuild... Thanks for the ebuild and answer...
(In reply to comment #47) > (In reply to comment #46) > > My guess would be that you ran out of heap space, the Eclipse Compiler threw an > > OutOfMemoryError, and Ant caught it as an InvocationTargetException. It's > > disappointing that Ant doesn't print the chained cause of the ITE, so we can't > > know for sure. > > You were right, because when I tried to compile eclipse in verbose mode (add > '-v' argument to ant) it showed me this exception - OutOfMemoryError. > (part of verbose log - http://wklej.to/u90q). > > > The JVM seems to employ some voodoo for determining its default heap > > parameters, most probably based on your total and free amounts of system > > memory. How much do you have? Could you try running the ebuild from a > > text-mode console without X or any other applications running? > > I have 1 GB RAM and 1,5 GB. > I have solved this problem by adding ANT_OPTS="-Xmx512M" before 'ant > insertBuildId compile' (it was in ebuild for previous version) and it worked. > You could add it to ebuild... > > Thanks for the ebuild and answer... > I found this page googling for a similar "build.xml" errors trying to emerge eclipse-sdk. I eventually caught an error message, that was scrolling out of the terminal window, saying eclipse-ecj was not found. After emerging that, the build.xml errors went away and everything compiled. USE="java6" emerge -v eclipse-ecj USE="java6" emerge -v eclipse-sdk The first time through I also added 'ANT_OPTS="-Xmx512M"'. I was able to re-emerge the sdk without that option, so it might not be needed.
(In reply to comment #48) > I found this page googling for a similar "build.xml" errors trying to emerge > eclipse-sdk. I eventually caught an error message, that was scrolling out of > the terminal window, saying eclipse-ecj was not found. After emerging that, > the build.xml errors went away and everything compiled. The Eclipse 3.4.2 ebuild on this page requires (and states a dependency on) ECJ. You should not have needed to emerge it explicitly unless you removed the dependency from the ebuild or were trying to merge it manually without allowing 'emerge' to calculate and satisfy dependencies. The Eclipse 3.5 and 3.5.1 ebuilds at bug #275375 do not require ECJ to be installed because they build and use their own.
Since eclipse-sdk-3.5.1 is in tree can this bug be closed?
Yes. Thanks.
Please bump 3.4 slot to 3.4.2, since there is a slot for 3.4, and 3.4.2 is the current 3.4 release. The current 3.4 package in portage has a software-update bug, that makes it hard to install plugins. This bug was solved in the 3.4.2 release.
(In reply to comment #52) > Please bump 3.4 slot to 3.4.2, since there is a slot for 3.4, and 3.4.2 is the > current 3.4 release. > > The current 3.4 package in portage has a software-update bug, that makes it > hard to install plugins. > > This bug was solved in the 3.4.2 release. > Would 3.5 not suffice? It is in the process of being stablised (amd64 done already). My plan was to remove the 3.4 slot soon.
(In reply to comment #53) > (In reply to comment #52) > > Please bump 3.4 slot to 3.4.2, since there is a slot for 3.4, and 3.4.2 is the > > current 3.4 release. > > > > The current 3.4 package in portage has a software-update bug, that makes it > > hard to install plugins. > > > > This bug was solved in the 3.4.2 release. > > > > Would 3.5 not suffice? It is in the process of being stablised (amd64 done > already). My plan was to remove the 3.4 slot soon. > My development team has standardized on 3.4.2 release, and are not ready to move to 3.5 series. I ran into problems with using the eclipse-SDK-3.4.2-linux-gtk.tar.gz tarball, and gentoo forum told me if I want any help, I need to stick with pakcages in portage. I feel kind of pinched.
(In reply to comment #54) > My development team has standardized on 3.4.2 release, and are not ready to > move to 3.5 series. I ran into problems with using the > eclipse-SDK-3.4.2-linux-gtk.tar.gz tarball, and gentoo forum told me if I want > any help, I need to stick with pakcages in portage. I feel kind of pinched. You mean GUI problems (clicking mouse on buttons not working etc?) that occur with gtk+-2.18 ? Either run it with GDK_NATIVE_WINDOWS=1 or upgrade to 3.5.2...
When I start eclipse, just after the splash screen, an empty dialog box appears with no buttons, and the workspace never opens. I have to kill the eclipse process form another terminal, and workspace/.metadata/.log shows the errror: !ENTRY org.eclipse.ui.workbench 4 0 2010-03-23 08:36:42.810 !MESSAGE Widget disposed too early! !STACK 0 java.lang.RuntimeException: Widget disposed too early! at org.eclipse.ui.internal.WorkbenchPartReference$1.widgetDisposed(WorkbenchPartReference.java:171) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:117) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1158) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1182) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1163) at org.eclipse.swt.widgets.Widget.release(Widget.java:1026) at org.eclipse.swt.widgets.Control.release(Control.java:3221) at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:1184) at org.eclipse.swt.widgets.Widget.release(Widget.java:1029) at org.eclipse.swt.widgets.Control.release(Control.java:3221) at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:1184) at org.eclipse.swt.widgets.Widget.release(Widget.java:1029) at org.eclipse.swt.widgets.Control.release(Control.java:3221) at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:1184) at org.eclipse.swt.widgets.Canvas.releaseChildren(Canvas.java:211) at org.eclipse.swt.widgets.Decorations.releaseChildren(Decorations.java:466) at org.eclipse.swt.widgets.Shell.releaseChildren(Shell.java:1948) at org.eclipse.swt.widgets.Widget.release(Widget.java:1029) at org.eclipse.swt.widgets.Control.release(Control.java:3221) at org.eclipse.swt.widgets.Widget.dispose(Widget.java:442) at org.eclipse.swt.widgets.Shell.dispose(Shell.java:1893) at org.eclipse.swt.widgets.Display.release(Display.java:3083) at org.eclipse.swt.graphics.Device.dispose(Device.java:237) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:129) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:386) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504) at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
Did you try running it with: GDK_NATIVE_WINDOWS=true ./eclipse
Indeed, I did. I tried in two ways: As one line: GDK_NATIVE_WINDOWS=1 ${HOME}/eclipse-3.4.2/eclipse and as two lines: export GDK_NATIVE_WINDOWS=1 ${HOME}/eclipse-3.4.2/eclipse Each time, I deleted all previous workspaces
So is this the end of the line? Will there be no update to the 3.4 slot of eclipse-sdk package (bringing the stop to the current 3.4.2)?
(In reply to comment #59) > So is this the end of the line? > Will there be no update to the 3.4 slot of eclipse-sdk package (bringing the > stop to the current 3.4.2)? > Would you be able to test the eclipse-sdk-3.4.2 ebuild in the tarball that matt attached. I believe that all the other deps will be in the tree so you shouldn't need them (hopefully). The issue atm is that there is no-one to maintain eclipse. Even matt who did a fantastic job packaging eclipse lately is only interested as far as his use of it goes. He is not interested in maintaining it. Now if the eclipse-sdk-3.4.2 ebuild above works then I may consider putting it into the tree.
I ran into one problem testing. http://distfiles.gentoo.org/distfiles/ecjsrc-3.4.2.zip HTTP request sent, awaiting response... 404 Not Found http://download.eclipse.org/eclipse/downloads/drops/R-3.4.2-200902111700/ecjsrc-3.4.2.zip HTTP request sent, awaiting response... 404 Not Found http://download.eclipse.org/eclipse/downloads/drops/R-3.4.2-200902111700/swt-3.4.2-gtk-linux-x86.zip HTTP request sent, awaiting response... 404 Not Found
My development team has moved to eclipse-3.5.2. So I don't need this any more.
