From: jhugunin <jhugunin>
Date: Thu, 1 May 2003 00:21:51 +0000 (+0000)
Subject: Expected fix for issue of Class.forName differences
X-Git-Tag: V1_1_0_RC2~103
X-Git-Url: https://source.dussan.org/?a=commitdiff_plain;h=6f13b740e05074d74326294a5baa77db1dde215d;p=aspectj.git

Expected fix for issue of Class.forName differences
between IBM and SUN's JDKs -- not yet tested on IBMs JDK to confirm
---

diff --git a/weaver/src/org/aspectj/weaver/Member.java b/weaver/src/org/aspectj/weaver/Member.java
index 1b6c9aadf..7e3b2474f 100644
--- a/weaver/src/org/aspectj/weaver/Member.java
+++ b/weaver/src/org/aspectj/weaver/Member.java
@@ -702,7 +702,8 @@ public class Member implements Comparable {
 	protected String makeString(TypeX t) {
     	// this is the inverse of the odd behavior for Class.forName w/ arrays
     	if (t.isArray()) {
-    		return t.getSignature();
+    		// this behavior matches the string used by the eclipse compiler for Foo.class literals
+    		return t.getSignature().replace('/', '.');
     	} else {
     		return t.getName();
     	}