RE: [aspectj-users] AJDT Magical Disappearing classes...

["Ron Bodkin" <rbodkin@xxxxxxxxxxxxxx>]

Interesting... I've seen the problem on a project without any inpath entries
and with a Java 1.4 compliant project.

I will have to update to RC3 and the latest build ... hopefully we can
figure out the root cause and fix this issue...

-----Original Message-----
From: aspectj-users-bounces@xxxxxxxxxxx
[mailto:aspectj-users-bounces@xxxxxxxxxxx] On Behalf Of Matt Chapman
Sent: Tuesday, May 09, 2006 7:02 AM
To: aspectj-users@xxxxxxxxxxx
Subject: Re: [aspectj-users] AJDT Magical Disappearing classes...

Ron,

Thanks for the information, that should help narrow it down. See also
bug 132314 for a similar issue.

To help debug future occurrences of problems like this, I've made use
of the expanded event trace capabilities in AJDT 1.4 dev builds to add
a new trace category called "Compiler / Task list messages". This is
disabled by default, so needs to be enabled via the filters button of
the AJDT Event Trace view. This is only available in dev build
1.4.0.20060509092419 (or later) for Eclipse 3.2RC3.

Regards,

Matt.

On 09/05/06, Ron DiFrango <rdifrango@xxxxxxxxxxxxxxxxxxx> wrote:
> 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.
>
> Ron
>
> ________________________________
>
> From: aspectj-users-bounces@xxxxxxxxxxx on behalf of Ron Bodkin
> Sent: Tue 5/9/2006 2:25 AM
> To: aspectj-users@xxxxxxxxxxx
> 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
> To: aspectj-users@xxxxxxxxxxx
> Subject: [aspectj-users] AJDT Magical Disappearing classes...
> Importance: High
>
>
>
> 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:
>
> Eclipse SDK
>
> Version: 3.1.1
>
> Build id: M20050929-0840
>
> Eclipse AspectJ Development Tools
>
> Version: 1.3.1
>
> Build id: 20060410063641
>
> AspectJ version: 1.5.1a
>
> JDK:
>
> C:\Program Files\Java\jdk1.5.0_04
>
> 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.
>
> Ron
>
>
> _______________________________________________
> aspectj-users mailing list
> aspectj-users@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/aspectj-users
>
>
>
_______________________________________________
aspectj-users mailing list
aspectj-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/aspectj-users