RE: [ajdt-dev] AJDT Cross References not usable with multiple projects

["Sebastien Tardif" <stardif@xxxxxxxxxxxx>]

I have created enhancement -> https://bugs.eclipse.org/bugs/show_bug.cgi?id=287555

-----Original Message-----
From: ajdt-dev-bounces@xxxxxxxxxxx [mailto:ajdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Andrew Eisenberg
Sent: Tuesday, August 25, 2009 12:33 AM
To: ajdt-dev@xxxxxxxxxxx
Subject: Re: [ajdt-dev] AJDT Cross References not usable with multiple projects

You are describing a known limitation of AJDT that in path and aspect
path references are only one way.  I.e., the project consuming the in
path or aspect path knows about the references, but the other project
does not.

What you see in the XRef view is a projection of the underlying
crosscutting model that is maintained by the AspectJ compiler.  It is
the same model that is used to create the gutter markers in editors.
Each project keeps track of its own crosscutting model and anything in
the xref view comes from that project's model.

The problem that you are seeing is that the crosscutting model for
Project Framework does not contain the elements created when that
project was woven into Project EJB.  This is because Project
Framework's model was generated without any references to Project EJB
(since that is how it was compiled).  Whereas Project EJB's
crosscutting model does contain references to Project Framework since
it was compiled and woven against Project Framework.

So far, we have not tried to solve this problem.  It would require
some significant infrastructure to maintain and manage inter-project
references.  It is worth opening an enhancement request on bugzilla so
that we can discuss possible solutions.

On Mon, Aug 24, 2009 at 4:52 PM, Sebastien Tardif<stardif@xxxxxxxxxxxx> wrote:
> I'm using Eclipse 3.4.1 with 2.0.0.e34x-20090622-2000 and still having the
> same problem I had 2 years ago with Cross References view.
>
>
>
> The problem is caused by scoping Cross References view to the current
> project when the focuse is against an Aspect that apply to lot of projects.
>
>
>
> The fix is to code Cross References view when focused on an Aspect to be
> like the Problem view. Problem view has scope options, current project,
> working set, and others.
>
>
>
>  Example of the problem:
>
>
>
> Project Framework
>
>   MyAspect.aj
>
>
>
> Project EJB
>
>   AspectJ Path -> Project Framework
>
>
>
> With this setup, when I'm on a class of project EJB that is modified by
> MyAspect.aj I see something in Cross References view. However, when I focus
> on MyAspect.aj in project framework I don't see my classes that are touched
> by the aspect.
>
>
>
> That seems to me to be a simple and reasonable project setup.
>
>
>
> Thinking about it, what is the difficulty to keep track in a Map for each
> AspectJ the list of Java classes modified if we are able to show the aspects
> when the focus is on a class?
>
> _______________________________________________
> ajdt-dev mailing list
> ajdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/ajdt-dev
>
>
_______________________________________________
ajdt-dev mailing list
ajdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ajdt-dev