Hi, You don't need to set minimal model and type demotion any more, those all default to true now.
overweaving mode will ignore the key (as it doesn't need to go back to the original form of the class file), so I'm not surprised to see the key problem vanish when you turn it on, but I am surprised that is does nothing after that. Can you share the project with me? cheers, Andy On 27 April 2013 10:30, aryenneb <aryen...@hotmail.com> wrote: > Hi Andy, > Thanks again for responding. I tried using shorter file names (to less > than > 10 letters), but that did not help. I was wondering if there might be > something wrong with my Eclipse AspectJ options, so I tried using these: > -Xset:overWeaving=true,-Xset:minimalModel=true,typeDemotion=true along with > 'incremental compiler optimizations' but nothing has helped so far. > > The situation is still, that with more input files, using the > -Xset:overWeaving=true gives the wrong output. It is as if all of the > processing is just bypassed. Removing this option just continues to give > the 'missing key' error. However, a smaller number of input files works > correctly with the options ,-Xset:minimalModel=true,typeDemotion=true and > 'incremental compiler optimizations'. > > By the way I am using Eclipse Juno, AspectJ 1.7 and JDK 1.7. > > Thanks for your help. > Aryenne > > > > -- > View this message in context: > http://aspectj.2085585.n4.nabble.com/Aspectj-error-Internal-compiler-error-java-lang-RuntimeException-key-not-found-in-wovenClassFile-at--tp4650879p4650919.html > Sent from the AspectJ - users mailing list archive at Nabble.com. > _______________________________________________ > aspectj-users mailing list > aspectj-users@eclipse.org > https://dev.eclipse.org/mailman/listinfo/aspectj-users >
_______________________________________________ aspectj-users mailing list aspectj-users@eclipse.org https://dev.eclipse.org/mailman/listinfo/aspectj-users
