Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [aspectj-users] Cflow and enums


Hi,

'Cant find type' is perhaps our most painful error message as in many
cases it omits any useful context.  As you are using enums and a recent
dev build, I presume you are binary weaving some aspects into some java5
code you have previously built with javac?  Can you download the most
recent dev build and give it a go compiling completely from source?  Since
last nights build the ajc dev builds can now process all Java 5 features
from source if you supply the '-1.5' flag.  You should run ajc on a 1.5
JRE if you are going to use 1.5 features.

It is only looking for the types in doing it's analysis, it won't
necessarily weave into them - are you able to ensure they are on
the classpath (they don't have to be on the inpath or anything) to
keep type resolution happy?

Perhaps think of it like this, in order to compile any Java
program you need rt.jar (or equivalent) and any other classes
you reference on your classpath so the java compiler can
perform type analysis.  Ajc is expecting the same (even if binary
weaving), it needs access to types you have referenced in
order to determine what is/isnt a match.

cheers,
Andy.
---
Andy Clement
AspectJ
clemas@xxxxxxxxxx



"Nitzan Volman" <nitzan@xxxxxxxxxxx>
Sent by: aspectj-users-admin@xxxxxxxxxxx

18/01/2005 16:52

Please respond to
aspectj-users@xxxxxxxxxxx

To
<aspectj-users@xxxxxxxxxxx>
cc
Subject
[aspectj-users] Cflow and enums





Hi,

I have encountered the following problem.

When defining a pointcut which includes either cflow or call it seems the weaver attempts to find/advise every enum I defined in my code,

and fails with the following message:

..\MyClass.class [error] can't find type …MyEnum

(no source information available)

I am using a Dev build downloaded a few days ago.

What am I doing wrong?

/Nitzan


Back to the top