This is the mail archive of the
java-patches@gcc.gnu.org
mailing list for the Java project.
[gui][patch] monthly merge from java-gui-branch
- From: "graydon hoare" <graydon at redhat dot com>
- To: "java-patches.gcc.gnu.org" <java-patches at gcc dot gnu dot org>
- Cc: classpath at gnu dot org
- Date: Wed, 21 Jul 2004 22:51:20 -0400
- Subject: [gui][patch] monthly merge from java-gui-branch
- Organization: red hat
hi,
this is the "monthly" merge from java-gui-branch to gcc trunk. this will
be the last such regularly scheduled merge for a while; we're going to
be taking a slightly less disruptive (to trunk) route for a bit, as an
experiment: merging between the gui branch and classpath directly more
frequently, and doing a 1-way merge into trunk at lower frequency (say
every 2-3 months). this is primarily to reduce the number of times we
risk breaking the gcc trunk build, which is a recurrent problem of mine.
I'd ask that future work on gui-related stuff go into the gui branch
or classpath, *not* gcc trunk, since this will ease integration and
reduce the risk of a merge clobbering your changes.
anyways, the july patch is here:
http://people.redhat.com/graydon/java-gui-merge-july-20-2004.patch
it's another 600k of diffs, all confined to java.awt, javax.swing, and
jni/gtk-peers. I've done a build test against the trunk and run the
recent "activityboard" test:
http://people.redhat.com/graydon/activityboard.java
which appears to work out of the box with it. please let me know if you
have any objections; I'll be committing shortly (say, tomorrow morning)
if not. I'd welcome anyone with an extra autobuilder and some spare cycles
to check it out and make sure I'm not causing any trouble. last time was
almost too frustrating for me to believe my own test results anymore.
-graydon