Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 359384 - org.aspectj.weaver.MissingResolvedTypeWithKnownSignature cannot be cast to org.aspectj.weaver.ReferenceType
Summary: org.aspectj.weaver.MissingResolvedTypeWithKnownSignature cannot be cast to or...
Status: RESOLVED FIXED
Alias: None
Product: AJDT
Classification: Tools
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: 2.2.0   Edit
Assignee: AJDT-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-29 05:41 EDT by Ivica Loncar CLA
Modified: 2011-11-07 16:25 EST (History)
2 users (show)

See Also:

Attachments
stacktrace (4.48 KB, text/plain)
2011-09-29 07:34 EDT, Ivica Loncar CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ivica Loncar CLA 2011-09-29 05:41:12 EDT 
Build Identifier: 


I've got following exception when compiling code:

java.lang.ClassCastException
at org.aspectj.weaver.World.resolveGenericWildcardFor(World.java:565)
at org.aspectj.weaver.World.resolveToReferenceType(World.java:460)
at org.aspectj.weaver.World.resolve(World.java:309)
at org.aspectj.weaver.World.resolve(World.java:219)
at org.aspectj.weaver.World.resolve(World.java:254)
at org.aspectj.weaver.TypeFactory.createParameterizedType(TypeFactory.java:42)
at org.aspectj.weaver.World.resolveTo ... 
Compile error: ClassCastException thrown: org.aspectj.weaver.MissingResolvedTypeWithKnownSignature cannot be cast to org.aspectj.weaver.ReferenceType


I have enabled non standard compiler options:

-Xset:minimalModel=true,typeDemotion=true



Reproducible: Sometimes

Steps to Reproduce:
1. cannot reproduce always
Comment 1 Ivica Loncar CLA 2011-09-29 05:47:16 EDT 
SpringSource Tool Suite 

Version: 2.7.2.RELEASE
Build Id: 201109131000


Eclipse AspectJ Development Tools

Version: 2.1.3.e37x-20110628-1900
AspectJ version: 1.6.12.20110613132200
Comment 2 Ivica Loncar CLA 2011-09-29 07:34:32 EDT 
Created attachment 204282 [details]
stacktrace
Comment 3 Andrew Clement CLA 2011-09-29 12:38:54 EDT 
Hi.  I would recommend updating to a new version of AJDT.  I can see that code is still the same in latest but possibly some other stuff has been modified.  In particular the non-standard options you are running with are now on by default - and some issues had to be resolved before they could be made default, you might be hitting one of those.
Comment 4 Andrew Eisenberg CLA 2011-11-07 15:13:14 EST 
Any progress here?  Are you still having the problem?
Comment 5 Ivica Loncar CLA 2011-11-07 16:01:53 EST 
Hi Andrew!

I've removed compiler options and I don't notice that many problems with AJDT anymore. This might be also related with my attempt to use APT builder (querydsl) in the same project with AJDT.
Comment 6 Andrew Eisenberg CLA 2011-11-07 16:25:18 EST 
Thanks for getting back to me.  Resolving.

It could be related to APT.  There is only partial support for APT in AJDT right now.