Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[Fwd: Re: [aspectj-users] Internal compiler error "org.aspectj.weaver.BCException: Bad type name:"]
I found that the cause of the whole trouble really was the "Compiler compliance level" (Preferences > Java > Compiler) which was set to 5.0. After I downgrade it to 1.4, the problem is solved... Sorry for the confusion. Thanks!

-------- Original Message --------
Subject: Re: [aspectj-users] Internal compiler error "org.aspectj.weaver.BCException: Bad type name:"
Date: Tue, 01 Feb 2005 09:59:36 -0500
From: Dmitri Mamrukov <dym@xxxxxxx>
Reply-To: aspectj-users@xxxxxxxxxxx
To: aspectj-users@xxxxxxxxxxx
References: <OFAE5150CE.C749F388-ON80256F9B.003C4287-80256F9B.003CC573@xxxxxxxxxx>


Yes, the same situation. And after commenting out the body of the aspect ComparablePoint the error goes away (though I had to make sure that compilation fully completes by cleaning/rebuilding the project).

Well, I'd like to note one strangeness as well. The classpath variable ASPECTJRT_LIB would normally (after creating AspectJ projects or adding examples via File > New > Other > AspectJ > AspectJ Examples) specify the correct path <ECLIPSE_HOME>/plugins/org.aspectj.runtime_1.5.0.20050124144759/aspectjrt.jar but with a forward slash in front of <ECLIPSE_HOME>. That is, /c:/opt/eclipse/plugins/org.aspectj.runtime_1.5.0.20050124144759/aspectjrt.jar. So to facilitate compilation, I had to manually remove the forward slash by editing the classpath variable in the Project Properties.

Since you and another person (pope) assert that you don't encounter any internal compiler error, I think that it would be helpful to reinstall AspectJ, Eclipse, & AJDT and clear the workspace. Just to see what happens. Though I've not had any particular problems with playing with other aspects examples.

I have an impression that the error comes up when one or more aspects state "declare parents:" for a single class to implement some interface. Here a pre-Tiger version of implementing of the Comparable interface is used. Is there any possible problem with this? I've tried "Comparable<Point>" but it didn't work in the aspect (I guess at this moment developers are working on Tiger compatibility). However, after commenting out the body of the ComparablePoint aspect and modifying the Point class to directly implement "Comparable<Point>", it worked fine.

Matt Chapman wrote: 
Dmitri Mamrukov <dym@xxxxxxx> wrote on 01/02/2005 04:25:17:
  
Yes, I did respect the package names (I checked that too :-)). I just 
copied the folder <Install-Dir>/doc/examples/introduction with its 
contents into my folder src.

The problem ("Internal compiler error..." + pop-up dialogs for this 
error) goes away when I comment out the whole body of the aspect 
ComparablePoint. That is,

public aspect ComparablePoint
{
}

This way, I've been able to run the examples (the main methods in each 
of the aspects and the Point class).
    
Clearly the internal compiler error means there is a bug here somewhere, 
but I haven't been able to reproduce it either. There is an easier way to 
add these examples to your eclipse workspace, which is to do File > New > 
Other > AspectJ > AspectJ Examples. If you do this, do you still get the 
same error?

Regards,

Matt.


_______________________________________________
aspectj-users mailing list
aspectj-users@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/aspectj-users

_______________________________________________ aspectj-users mailing list aspectj-users@xxxxxxxxxxx http://dev.eclipse.org/mailman/listinfo/aspectj-users

Back to the top