From: "Andrew John Hughes" <gnu_andrew@member.fsf.org>
To: mauve-patches@sources.redhat.com
Subject: FYI: Testcase fix
Date: Tue, 19 Feb 2008 23:04:00 -0000 [thread overview]
Message-ID: <20080219230330.GA5942@localhost.localdomain> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 469 bytes --]
This patch fixes the TargetedNotification test
to not use a null object; this causes an exception
from java.util.EventSource.
ChangeLog:
2008-02-10 Andrew John Hughes <gnu_andrew@member.fsf.org>
* gnu/testlet/javax/management/remote/TargetedNotificationTest.java:
Avoid using null for the event object.
--
Andrew :)
Support Free Java!
Contribute to GNU Classpath and the OpenJDK
http://www.gnu.org/software/classpath
http://openjdk.java.net
[-- Attachment #1.2: management-07b.diff --]
[-- Type: text/x-diff, Size: 801 bytes --]
Index: gnu/testlet/javax/management/remote/TargetedNotificationTest.java
===================================================================
RCS file: /cvs/mauve/mauve/gnu/testlet/javax/management/remote/TargetedNotificationTest.java,v
retrieving revision 1.1
diff -u -3 -p -u -r1.1 TargetedNotificationTest.java
--- gnu/testlet/javax/management/remote/TargetedNotificationTest.java 10 Feb 2008 23:33:38 -0000 1.1
+++ gnu/testlet/javax/management/remote/TargetedNotificationTest.java 19 Feb 2008 22:54:53 -0000
@@ -34,7 +34,7 @@ public class TargetedNotificationTest
public void test(TestHarness h)
{
TargetedNotification tn;
- Notification n = new Notification("", null, 1);
+ Notification n = new Notification("", this, 1);
h.checkPoint("Constructor tests");
try
{
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
reply other threads:[~2008-02-19 23:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080219230330.GA5942@localhost.localdomain \
--to=gnu_andrew@member.fsf.org \
--cc=mauve-patches@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).