From 876e7d62bb8cd5313377adaf02db372a1e539b82 Mon Sep 17 00:00:00 2001
From: aclement <aclement>
Date: Tue, 19 Feb 2008 22:01:33 +0000
Subject: [PATCH] 204505: testcode and fix: poorly documented method in
 ResolvedMemberImpl now creates a sig based on the erasure of the type
 variable rather than using the type variable itself.  Passes this case but
 could be related situations that fail...

---
 weaver/src/org/aspectj/weaver/ResolvedMemberImpl.java | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/weaver/src/org/aspectj/weaver/ResolvedMemberImpl.java b/weaver/src/org/aspectj/weaver/ResolvedMemberImpl.java
index 039d9f5c5..2075f84aa 100644
--- a/weaver/src/org/aspectj/weaver/ResolvedMemberImpl.java
+++ b/weaver/src/org/aspectj/weaver/ResolvedMemberImpl.java
@@ -920,7 +920,9 @@ public class ResolvedMemberImpl extends MemberImpl implements IHasPosition, Anno
 	// comparison.
 	private void appendSigWithTypeVarBoundsRemoved(UnresolvedType aType, StringBuffer toBuffer) {
 		if (aType.isTypeVariableReference()) {
-			toBuffer.append("T;");
+			// pr204505
+			appendSigWithTypeVarBoundsRemoved(aType.getUpperBound(),toBuffer);
+//			toBuffer.append("T;");
 		} else if (aType.isParameterizedType()) {
 			toBuffer.append(aType.getRawType().getSignature());
 			toBuffer.append("<");
-- 
2.39.5