Glad to hear I am not the only one. I can narrow it down to one of the following situations:
1) Jar file on InPath is dependent upon an external jar and you do not have it associated with your project.
2 Or in my case, I think it is puking [without telling me] because the library I am weaving into is not compatible with JDK 1.5 because it has variables name enum and it should not.
Fortunately for me, this library is "Open Source", so I am just going to include it on my project. But it should would be nice to have this fixed ASAP.
From: aspectj-users-bounces@xxxxxxxxxxx on behalf of Ron Bodkin
Sent: Tue 5/9/2006 2:25 AM
Subject: RE: [aspectj-users] AJDT Magical Disappearing classes...
It's been a significant problem for me too, although I haven't had a chance to narrow it down. In my case, the best approach is to run ant builds to find out the compiler error.
From: aspectj-users-bounces@xxxxxxxxxxx [mailto:aspectj-users-bounces@xxxxxxxxxxx] On Behalf Of Ron DiFrango
Sent: Monday, May 08, 2006 9:04 PM
Subject: [aspectj-users] AJDT Magical Disappearing classes...
AJDT Dev Team.
I am experiencing an interesting phenomon, if the AJDT compile experiences an issue during a compile, it just flat out stops and does not emit an error message.
My configuration is as follows:
Build id: M20050929-0840
Eclipse AspectJ Development Tools
Build id: 20060410063641
AspectJ version: 1.5.1a
I have partiallly got around this for source cod by making it temporarily a Java project then get the "real" compiler errors. Correcting them and re-enabling the Aspectj Nature. But for aspects that apply to JAR's on the InPath this does not work.
Any thoughts as this is really hindering my progress.
aspectj-users mailing list