Re: [aspectj-users] Problems with Building -- Exporting aspects across m

["Andy Clement" <andrew.clement@xxxxxxxxx>]

How are your projects configured? Did you go for aspectpath or inpath?
 So you have AJDT Project A  and Java Project B with B depending on A
via aspectpath ?  You make the change where ? to java code in A or B?

 Are you on a recent version of AJDT (I made some changes to
incremental compilation recently).

To understand what is/isnt getting built you can activate the AJDT
Event Trace view in eclipse, turn on full reporting of all types of
event (button in top right) and then when you make your change it will
tell you everything it is doing. Does something in there not look
right?

Andy.

On 11/04/2008, Mike Schneider <mikepschneider@xxxxxxxxx> wrote:
> Thanks Andy.  I basically figured out the same thing after some
>  hunting.  This technique works and it shows the correct markers in my
>  code.
>
>  However, I have a second problem.  Now when I run my code within
>  eclipse it does not pick up my recent changes to the java
>  files without doing a clean.  For instance, I have a unit test that
>  passes.  I update some of the data inputted to the unit test
>  such that it shouldn't pass.   I run it again (with build
>  automatically turned on) and it still passes.  I do a full clean,
>  allow the
>  rebuild to run, and run it again, and the test fails.  The only
>  solution I have currently is to disable aspects, or to do a full clean
>  each time
>  I execute.
>
>  Any idea what's going on here, and how I can fix it?    Thanks
>
>  Mike
>
>
>  On Mon, Apr 7, 2008 at 9:28 AM, Andy Clement <andrew.clement@xxxxxxxxx> wrote:
>  > Hello Mike,
>  >
>  >  Aspects from a project upon which you depend are not automatically
>  >  picked up unless they can be found on the aspect path for the project
>  >  you want to get woven.
>  >
>  >
>  >  > I also tried adding the folder
>  >  >  containing the .aj files to the Inpath of the derived project and the
>  >  >  AspectJ path of the derived project.
>  >
>  >  Like classpath, the inpath and aspectpath are for jars and directories
>  >  containing class files, not source files.  You need to put the bin
>  >  folder of the project where the aspects are built onto the aspectpath
>  >  of the projects you want to be woven. ( I know this could be more UI
>  >  friendly and involve some simple clicks rather than path
>  >  configuration).  With the compiled aspects on the aspectpath, the
>  >  projects will get woven.  Now, showing across project markers is quite
>  >  complicated (perhaps I mean  'not always 100% reliable' ....) so the
>  >  best way to verify your code is woven as you expect is to run your
>  >  tests.  Or you could turn on the weave info messages in the UI and
>  >  then information about what gets woven will come out in the problems
>  >  view as info messages.
>  >
>  >  Andy.
>  >  _______________________________________________
>  >  aspectj-users mailing list
>  >  aspectj-users@xxxxxxxxxxx
>  >  https://dev.eclipse.org/mailman/listinfo/aspectj-users
>  >
>  _______________________________________________
>  aspectj-users mailing list
>  aspectj-users@xxxxxxxxxxx
>  https://dev.eclipse.org/mailman/listinfo/aspectj-users
>