Changelog for
eclipse-platform-3.0.2-8.x86_64.rpm :
Fri Aug 12 00:00:00 2005 Jeff Pound
3.0.2-8
- Use mozilla version 1.7.10.
Sat Aug 6 00:00:00 2005 Andrew Overholt 3.0.2-7
- Build libswt-mozilla-gtk.so.
- Add patch for API change between mozilla 1.6 and 1.7.7.
Tue Jul 19 00:00:00 2005 Andrew Overholt 3.0.2-6
- Add XTEST_LIB_PATH on x86_64 to stop unsatisfied link errors.
- Add xorg-x11-devel build requirement.
- BuildRequire java-devel (not java).
- Minor tweaks courtesy JPackage.org.
- Remove junit requirement (since we\'re using all Eclipse.org jars).
Wed Jun 22 00:00:00 2005 Aaron Luchko 3.0.2-5
- Fixed permissions on /usr/lib64/eclipse/eclipse and /usr/bin/eclipse
Wed Jun 22 00:00:00 2005 Andrew Overholt 3.0.2-4
- Add x86_64.
Sat Jun 4 00:00:00 2005 Andrew Overholt 3.0.2-3
- Update to new (as in Fedora Core 4) sub-RPM layout.
Wed May 25 00:00:00 2005 Ben Konrath 3.0.2-2
- Don\'t use 2 for plugin names.
Fri Apr 22 00:00:00 2005 Ben Konrath 3.0.2-1
- Update sources to 3.0.2.
- Update SWT patches.
Wed Mar 30 00:00:00 2005 Andrew Overholt 3.0.1-12
- Bump release.
- Remove old changelog entries (< 3.0.1).
- Add 64-bit awareness to SWT jar locations.
Fri Mar 18 23:00:00 2005 Jeff Pound 3.0.1-6
- Remove ia64 from xml workaround loop.
Wed Jan 5 23:00:00 2005 Aaron Luchko 3.0.1-5
- fixed problem in search.patch
- added search.patch a backported bugfix from 3.1.0
- added charsets.patch to accommodate improper encodings and ibm jvm
Mon Dec 6 23:00:00 2004 Aaron Luchko 3.0.1-4
- changed eclipse.script to use /usr/bin/java when no jvm is supplied
Mon Nov 22 23:00:00 2004 Ben Konrath 3.0.1-3
- split cvs-permission-bits.patch in two
- bug fix for cvs-permission-bits.patch
Sat Oct 30 00:00:00 2004 Ben Konrath 3.0.1-2
- add symlink for releng plugins that rely on o.e.pde.build_3.0.0
Sat Oct 30 00:00:00 2004 Ben Konrath 3.0.1-1
- updated to Eclipse 3.0.1
- updated jnigen patch
- removed some debugging print statements
- updated Red Hat documentaion sources
- added Red Hat documentation pdf
- remove commented ftp-webdav stuff as it will be in it\'s own spec file