I've been working on a package for 3.4 since RC1. I just uploaded a source package to my [[https://launchpad.net/~rock-gimp/+archive ppa]]. It is based off of the never-released packaging for 3.3 in debian's pkg- java svn. There are a few major issues:
* Help indexing causes memory corruption, which leads to a crash. This seems to be a gcj-4.2 issue; other jvms don't seem to have this problem. Unfortunately, the source package is set up to build with gcj, so some of the help file packages never get built. Furthermore, if you try to search help files installed using the update manager while running under gcj, eclipse crashes. * The Eclipse source build lost the ability to compile the SWT native libraries sometime between RC1 and the final release. This package uses the .so files that come in the upstream tarball. * There are several jars that were replaced with symlinks to jars in /usr/share/java. Since the 3.4 versions have had osgi properties added to their manifests, this isn't a safe transformation anymore, so those files aren't replaced with symlinks anymore. * P2 doesn't work. If you enable classic update, you can still use it to install new plugins from update sites. Despite all that, I've found it to be reasonably stable and much more useful to me than the 3.2 packages in Hardy. -- Upgrade to Eclipse 3.4 https://bugs.launchpad.net/bugs/123064 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
