Hi, Le lundi 25 juin 2012 23:34:39, Erich Schubert a écrit : > Certain actions (I'm no sure which one, I havn't been able to reproduce > them reliably) will cause this message to be printed. This does not > happen with OpenJDK6, and it did not happen in Sun Java6. > I've seen them occur in multiple applications, for example in current > MediathekView, from http://zdfmediathk.sourceforge.net/
I've been unable to reproduce this reliably... Did this append often with MediathekView ? > See also: > http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7130140 > http://hg.openjdk.java.net/jdk7/2d/jdk/diff/3b9a288d7ddb/src/share/classes/ > java/awt/event/MouseEvent.java So it is indeed a OpenJDK string, and not an > application string. > And clearly, this class should not be using System.out.println, but instead > use the logging API. I fully agree with you : System.out usage in java.* packages should be reduced to a strict minimum. > According to the bug report, it should happen in any applications when > using mouse scroll. I could not reproduce it again right now, not as > easily. But I did not try the mentioned example from the bug. It seems > that this has been partially fixed, but there are still situations where > it occurs. > It should be trackable down using the unqiue string easily (and it probably > is in MouseEvent.java) > > This is a related JDK8 changeset: > http://hg.openjdk.java.net/jdk8/awt/jdk/rev/19431d07bc19 > > But I do not get OpenJDK Mecurial, I'm unable to find out where to see the > current JDK source. Most of the stuff is last modified 4 years ago. > The SCM is completely inaccessible to outsiders, and I was unable to find > what the changelog of MouseEvent.java for OpenJDK7 is. > If above patch applies to the current JDK7, it should be a no-brainer to > add. Here is link to upstream JDK7 / JDK8 : http://hg.openjdk.java.net/jdk7u/jdk7u- dev/jdk/log/tip/src/share/classes/java/awt/event/MouseEvent.java http://hg.openjdk.java.net/jdk8/jdk8/jdk/log/tip/src/share/classes/java/awt/event/MouseEvent.java => It's only fixed in JDK8 and not in recent update of JDK7. > While for me this bug is a mere annoyance, "System.out.println" inside AWT > is bound to cause some true bugs in other applications. I'm not sure this warrant a specific fix : there is lots of other System.out usage in JDK and this is just annoyance... Cheers, -- Damien _______________________________________________ Mailing list: https://launchpad.net/~openjdk Post to : [email protected] Unsubscribe : https://launchpad.net/~openjdk More help : https://help.launchpad.net/ListHelp
