Re: [aspectj-users] broken resources?

[Adrian Colyer <adrian.colyer@xxxxxxxxx>]

ok, if it works when we prevent the weaver from touching the file then
it must be something that the weaver is doing that somehow breaks the
native method down the line. I have no idea what that might be right
now though! Please could you raise a bug report and attach the
generated Builder.class file, the source for the aspect, and the
source for Builder (if that last one is difficult, we might be able to
work from just the .class file) and we can take a look.

Thks, A.

On 16/08/05, Torsten Curdt <tcurdt@xxxxxxxxxx> wrote:
> 
> On 16.08.2005, at 15:02, Adrian Colyer wrote:
> 
> > Can't see anything obviously sinister in the aspect, and the last
> > advice is quite some distance in the stack from the point of failure.
> > If you temporarily change the advice as follows:
> 
> I've added the exclusion of the Builder at the pointcut level.
> Now it works :-/ ...I could say "whatever - it works".
> ...but I really like to find out what the problem was/is.
> 
> How can I help to track that down?
> 
> cheers
> --
> Torsten
> 
> 
> _______________________________________________
> aspectj-users mailing list
> aspectj-users@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/aspectj-users
> 
> 
> 
> 


-- 
-- Adrian
adrian.colyer@xxxxxxxxx