[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [aspectj-users] Matching methods in a different module? 
Module B must be on Module A's Aspect path.  You can set this in the
project properties page.  However, since you are using maven, things
get a little trickier because maven also needs to understand what goes
on the aspect path.

You can take a look here for a bit about maven-aspectj/eclipse/ajdt integration.

2009/7/18 Eugeny N Dzhurinsky <bofh@xxxxxxxxxxx>:
> Hello!
>
> I am developing some multi-module project (maven-driven, if that matters). I
> do have the module A, which holds the definitions and implementations of DAO.
> In the module B there is a need to apply some advices to certain methods of
> the DAO objects.
>
> When I define an aspect in the module A, AJDT does report the correctness of
> the pointcut expression, and it reports the advised methods as well.
>
> However when I move the aspect to the module B - AJDT complains it can't find
> advised methods.
>
> Module A and module B are the projects in the workspace. Module B depends on
> module A. Both of these modules have the AspectJ capability enabled.
>
> So the question is - does AJDT tracks the classes, defined in the different
> project, which is the one the current project holding an advice depends on?
>
> --
> Eugene N Dzhurinsky
>
> _______________________________________________
> aspectj-users mailing list
> aspectj-users@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/aspectj-users
>
>