Bug 108889 - BCE Exception while adding "AspectJ nature" to Java project (ResolvedType.java:1500)
Summary: BCE Exception while adding "AspectJ nature" to Java project (ResolvedType.jav...
Status: RESOLVED FIXED
Alias: None
Product: AspectJ
Classification: Tools
Component: Compiler (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 1.5.0 M4   Edit
Assignee: Adrian Colyer CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-06 20:07 EDT by Dean Wampler CLA
Modified: 2005-10-28 07:00 EDT (History)
0 users

See Also:

Attachments
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 Dean Wampler CLA 2005-09-06 20:07:26 EDT 
I have a java project with ~30-40 classes, some of which use generics. I
attempted to add the aspectj nature and got the following exception dump:

!SESSION 2005-09-06 17:05:25.387 -----------------------------------------------
eclipse.buildId=I20050627-1435
java.version=1.5.0_04
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments:  -os win32 -ws win32 -arch x86

!ENTRY org.eclipse.ajdt.ui 4 0 2005-09-06 17:05:39.627
!MESSAGE BCException thrown: The type @missing@ is not parameterized or raw - it
has no generic type
!STACK 0
org.aspectj.weaver.BCException: The type @missing@ is not parameterized or raw -
it has no generic type
	at org.aspectj.weaver.ResolvedType.getGenericType(ResolvedType.java:1500)
	at
org.aspectj.ajdt.internal.compiler.lookup.EclipseFactory.fromBinding(EclipseFactory.java:236)
	at
org.aspectj.ajdt.internal.compiler.lookup.EclipseFactory.fromBindings(EclipseFactory.java:332)
	at
org.aspectj.ajdt.internal.compiler.lookup.EclipseFactory.fromBinding(EclipseFactory.java:254)
	at
org.aspectj.ajdt.internal.compiler.lookup.EclipseFactory.addSourceTypeBinding(EclipseFactory.java:745)
	at
org.aspectj.ajdt.internal.compiler.lookup.AjLookupEnvironment.completeTypeBindings(AjLookupEnvironment.java:116)
	at
org.aspectj.org.eclipse.jdt.internal.compiler.Compiler.beginToCompile(Compiler.java:301)
	at
org.aspectj.org.eclipse.jdt.internal.compiler.Compiler.compile(Compiler.java:315)
	at
org.aspectj.ajdt.internal.core.builder.AjBuildManager.performCompilation(AjBuildManager.java:728)
	at
org.aspectj.ajdt.internal.core.builder.AjBuildManager.doBuild(AjBuildManager.java:206)
	at
org.aspectj.ajdt.internal.core.builder.AjBuildManager.batchBuild(AjBuildManager.java:140)
	at org.aspectj.ajde.internal.CompilerAdapter.compile(CompilerAdapter.java:121)
	at
org.aspectj.ajde.internal.AspectJBuildManager$CompilerThread.run(AspectJBuildManager.java:191)

I have AJDT build 1.3.0.2005.0906130320; I also observed it with
1.3.0.20050902173422.

The source file it pukes on seems to change as I rearrange the project. As a
java project, it compiles without any warnings or errors.

I'll try to create an isolated case.
Comment 1 Matt Chapman CLA 2005-09-07 03:26:33 EDT 
Passing over to the compiler
Comment 2 Adrian Colyer CLA 2005-09-08 04:15:47 EDT 
tagging with M4...
(I think this may have been fixed in the compiler, but not yet integrated into
AJDT, will investigate).
Comment 3 Adrian Colyer CLA 2005-09-08 16:51:23 EDT 
I strongly suspect this is a duplicate of bug 108454, which is fixed in AspectJ but not yet incorporated into 
an AJDT build :- it should be available in AJDT on Monday. Please could you test out that AJDT when it is 
available and let me know? (Or you could just download the command-line compiler now if it's easy to 
build your project outside of AJDT...)

Thanks, Adrian.
Comment 4 Adrian Colyer CLA 2005-10-28 07:00:54 EDT 
I believe this is fixed - if you still see the problem in the latest builds please reopen.
Thanks, Adrian.