Hi all,
I'm facing an NPE inside AspectJ/AJDT. I can replicate it on my
project, but I'm trying to distill the smallest possible project
that causes the error.
It is connected with having another AJDT workspace project on the
inpath/aspecthpath. I can remember that recently AJDT introduced
some optimizations on handling multiple workspace projects, and I
can see it recompiling dependent projects when the a dependency is
modified, but cannot find a mention of these improvements in
release notes of 2.0.0 or 1.6.4 nor in bug reports. Can someone
point me to something describing how AJDT compiling of multiple
project has been enhanced so that I can try to push the right
buttons while trying to replicate the bug.
Thanks,
Simone
P.S. The exception stacktrace is :
java.lang.NullPointerException
at
org.aspectj.weaver.bcel.BcelAccessForInlineMunger.getMatchingSyntheticMember(BcelAccessForInlineMunger.java:109)
at
org.aspectj.weaver.ResolvedType.lookupSyntheticMember(ResolvedType.java:1850)
at org.aspectj.weaver.World.resolve(World.java:552)
at org.aspectj.weaver.MemberImpl.resolve(MemberImpl.java:80)
at
org.aspectj.weaver.bcel.BcelClassWeaver.matchInvokeInstruction(BcelClassWeaver.java:2936)
at org.aspe ... 217)
ARETURN
end public static String fromJavaName(String, int, String)
end public class org.apache.magma.website.utils.Binder
It happens multiple times in different classes.
-- Simone Gianni CEO Semeru s.r.l. Apache Committer
http://www.simonegianni.it/
_______________________________________________
ajdt-dev mailing list
