Comment 1 Hermann Voßeler 2007-03-13 17:26:26 EDT

Sorry --  copy-n-paste-error messed up the report.....



After upgrading to Eclipse 3.2.2 and AJDT 1.4.2.200703020612 the compiler
crashes. Small testproject works OK. 

Compiling our project externally with ANT/IAJC (using the aspectjtools.jar
from AspectJ1.5.2) works OK


------------stacktrace---------------
java.lang.IllegalStateException
at org.aspectj.weaver.ResolvedMemberImpl.parameterizedWith(ResolvedMemberImpl.java:616)
at org.aspectj.weaver.ResolvedMemberImpl.parameterizedWith(ResolvedMemberImpl.java:597)
at org.aspectj.weaver.ReferenceType.getDeclaredMethods(ReferenceType.java:512)
at org.aspectj.weaver.ResolvedType.addAndRecurse(ResolvedType.java:263)
at org.aspectj.weaver.ResolvedType.getMethodsWithoutIterator(ResolvedType.java:258)
at ... 3)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)

Compile error: IllegalStateException thrown: Wrong number of type parameters supplied

Comment 2 Andrew Clement 2007-03-14 04:15:32 EDT

Does it also work with the latest dev builds of AspectJ?  I think AJDT probably just needs an Aj upgrade to fix this.

Comment 3 Hermann Voßeler 2007-03-14 19:07:52 EDT

OK -- will check this when back on next Monday...

Comment 4 Hermann Voßeler 2007-03-19 17:39:18 EDT

Hello,

just re-checked our environment: we /did/ use a developement build. 
(because there seems to be no release build for Eclipse 3.2.2).
We used the update manager and got a build form 2.March 2007

Is there any newer dev build *for Eclipse 3.2.2* ? On the downloads
page, I see only the same build we used when we got the Exception.

Thanks,
Hermann Vosseler

Comment 5 Andrew Clement 2007-03-20 04:07:05 EDT

i dont believe there have been any updates to the compiler level in AJDT for a little while now - for AJDT on any level of eclipse.

Comment 6 Hermann Voßeler 2007-06-11 10:07:40 EDT

The situation with this bug has now changed (to be more dangerous for us):
It started to show up when using the ant task (outside eclipse) as well.
It apears on an irregular pattern and the Class reported as location varies as well. I tried to isolate some triggering pattern, but without any success: after stripping down about half of our project, the exception disapeares, but there seems to be no correlation to the parts of the code I removed. (Moreover, on machines with less memory it shows up almost regularily, while appearing only sporatically on the machine with 2GB.)

The good news is: the current version of AJDT for Eclipse 3.3 compiles without crash:
 Eclipse 3.3 Build id: I20070601-1539
 AJDT-Version: 1.5.0.200705301038
 AspectJ version: 1.5.4.200705211336


Same is true for the /old/ versions of (standalone) AspectJ <= 1.5.2a
While the newer Versions 1.5.3 and 1.5.3-DEV-20070228 exhibit the Crash

Comment 7 Hermann Voßeler 2007-06-11 10:11:30 EDT

Created attachment 70841 [details]
ajcore error log

ajcore from running <IAJC> within ANT 1.6.5 (standalone, without ECLIPSE)
using the aspecttools.jar from AspectJ 1.5.3-DEV-20070228

Comment 8 Andrew Clement 2007-11-08 11:13:12 EST

See bug 176991 and underlying problem 175039.  This was fixed on 3rd March - and drivers since then dont have this problem.

*** This bug has been marked as a duplicate of bug 176991 ***

Comment 9 Hermann Voßeler 2007-11-12 17:58:17 EST

yes, can confirm: since we switched over to the newer versions,
I haven't seen this stacktrace again...

Thanks for your work!
Hermann Vosseler