On 27/03/06, Scott <aspectj-users@xxxxxxxxxxx> wrote:
Yes. The working case is in the default package. I could move the classes into packages to see if that changes things.
If you can try your classes in a package other than the default ... that may change things...
Also, to make this more clear than my first email. AJDT appears to be working. It is the one in the Ant build (therefore, my code...) that is not working. I have replaced those jars with both the latest from the download site and with jars from my local machine (the ones that work). Still no go.
I am becoming more certain that it is some issue with the version that I am using, but I cannot find how to fix it. I appears that AJDT is working fine and well.
ANT uses the aspectjtools.jar
from a standard install of AspectJ. You won't be able to hack in the jars from an AJDT directly as ajde.jar+aspectjweaver.jar are not the same as aspectjtools.jar since some dependencies will be missing. If you put the AJDT
ajde.jar then the AJDT aspectjweaver.jar then the AspectJ aspectjtools.jar in that order on your ANT classpath... but as AspectJ is more recent than AJDT and no fixes have gone in for DeclareParents, they should be functionally equivalent in that area.
But first, before messing around with those paths, I'd recommend trying your AJDT scenario with the types in a package other than the default.
