Bug 93395 - NullPointerException after converting existing project
Summary: NullPointerException after converting existing project
Status: RESOLVED DUPLICATE of bug 92163
Alias: None
Product: AJDT
Classification: Tools
Component: Core (show other bugs)
Version: 1.2.0 M3   Edit
Hardware: PC Windows XP
: P3 critical (vote)
Target Milestone: ---   Edit
Assignee: AJDT-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-05-02 06:40 EDT by Chris Burnley CLA
Modified: 2005-05-03 04:46 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Burnley CLA 2005-05-02 06:40:23 EDT
Just reinstalled a clean Eclipse 3.1 M6 then installed AJDT 1.2.0 M2 and
converterted an existing java project to AspectJ, try to do anything including
building or ctrl-space and I get the following exception in the .log :

!ENTRY org.eclipse.ajdt.ui 4 0 2005-05-02 11:28:47.942
!MESSAGE NullPointerException thrown: null
!STACK 0
java.lang.NullPointerException
	at
org.aspectj.org.eclipse.jdt.internal.compiler.lookup.ClassScope.detectHierarchyCycle(ClassScope.java:945)
	at
org.aspectj.org.eclipse.jdt.internal.compiler.ast.ParameterizedSingleTypeReference.internalResolveType(ParameterizedSingleTypeReference.java:143)
	at
org.aspectj.org.eclipse.jdt.internal.compiler.ast.ParameterizedSingleTypeReference.resolveType(ParameterizedSingleTypeReference.java:208)
	at
org.aspectj.org.eclipse.jdt.internal.compiler.ast.TypeReference.resolveSuperType(TypeReference.java:112)
	at
org.aspectj.org.eclipse.jdt.internal.compiler.lookup.ClassScope.findSupertype(ClassScope.java:1092)
	at
org.aspectj.org.eclipse.jdt.internal.compiler.lookup.ClassScope.connectSuperclass(ClassScope.java:747)
	at
org.aspectj.org.eclipse.jdt.internal.compiler.lookup.ClassScope.connectTypeHierarchy(ClassScope.java:884)
	at
org.aspectj.org.eclipse.jdt.internal.compiler.lookup.CompilationUnitScope.connectTypeHierarchy(CompilationUnitScope.java:249)
	at
org.aspectj.ajdt.internal.compiler.lookup.AjLookupEnvironment.completeTypeBindings(AjLookupEnvironment.java:99)
	at
org.aspectj.org.eclipse.jdt.internal.compiler.Compiler.beginToCompile(Compiler.java:331)
	at
org.aspectj.org.eclipse.jdt.internal.compiler.Compiler.compile(Compiler.java:348)
	at
org.aspectj.ajdt.internal.core.builder.AjBuildManager.performCompilation(AjBuildManager.java:683)
	at
org.aspectj.ajdt.internal.core.builder.AjBuildManager.doBuild(AjBuildManager.java:168)
	at
org.aspectj.ajdt.internal.core.builder.AjBuildManager.batchBuild(AjBuildManager.java:102)
	at org.aspectj.ajde.internal.CompilerAdapter.compile(CompilerAdapter.java:122)
	at
org.aspectj.ajde.internal.AspectJBuildManager$CompilerThread.run(AspectJBuildManager.java:165)


After creating a clean AspectJ project, I don't seem to get the same error.
Comment 1 Matt Chapman CLA 2005-05-02 16:01:35 EDT
Chris,
That stack trace looks like a classic mis-matched level of Eclipse problem.
AJDT 1.2.0M2 for Eclipse 3.1 works only on Eclipse 3.1M3.
For 3.1M6 you want AJDT 1.2.0M3 for Eclipse 3.1 (note that there are also AJDT
versions for Eclipse 3.0).
Comment 2 Chris Burnley CLA 2005-05-02 16:05:18 EDT
Sorry I made a mistake and am actually running 1.2 M3 with eclipse 3.1 M6 and
I've tried the development build. Just about to try building in eclipse and
debug it.
Comment 3 Matt Chapman CLA 2005-05-02 16:09:43 EDT
You might actually have the Eclipse 3.0 version of AJDT. Try Window > Show View
> Other > AspectJ > AJDT EventTrace - it should say at startup.
Comment 4 Chris Burnley CLA 2005-05-02 16:14:42 EDT
21:04:57	 AJDT Plugin Startup
	AJDT version: 1.2.0 for Eclipse 3.1
	AspectJ Compiler version: DEVELOPMENT
	org.aspectj.ajdt.core.compiler.BuildOptions.showweavemessages = true
	org.aspectj.ajdt.core.compiler.BuildOptions.buildAsm = false
	org.eclipse.ajdt.ui.preferences.auto.migration.setting = true
	org.eclipse.ajdt.ui.objectopia-splice.ajproperties = build.ajproperties
	org.aspectj.ajdt.ui.compile-timeout = 120
	ajde.version.at.previous.startup = 1.5.0.20050413151050
	org.aspectj.ajdt.core.compiler.BuildOptions.incrementalMode = false
	org.eclipse.ajdt.ui.test-aspectj.ajproperties = build.ajproperties
	org.eclipse.ajdt.ui.preferences.ajdtPrefConfigDone = true
	org.eclipse.ajdt.ui.contracts.ajproperties = build.ajproperties
	org.eclipse.ajdt.ui.preferences.perform.auto.migration = true
	org.eclipse.ajdt.ui.contracts-web.ajproperties = build.ajproperties
	org.eclipse.ajdt.ui.preferences.prefRunForAjdtVersion = 1.2.0.20041214165937
21:04:57	 New version of AJDE detected (now:1.5.0.20050420095141) - checking
aspectjrt.jar for each project.


It is interesting that prefRunForAdjtVersion is 1.2.0.2004xxxx
Comment 5 Matt Chapman CLA 2005-05-03 04:46:22 EDT
Sorry, I jumped to conclusions after only a quick look at the stack trace. It is
in fact a compiler bug, already covered by 92163. It will hopefully be fixed
when AJC moves up to be based on the latest version of the JDT compiler.

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