Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Language IDEs » AspectJ » Multi-project compilation life cycle?
Multi-project compilation life cycle? [message #584713] Wed, 03 November 2004 19:02
Eclipse UserFriend
Originally posted by: srobertson.nvisia.com

Thanks again for the help Matt.

I was able to get this mostly working with AJDT 1.1.4 on WSAD 5.1.2 and
the AspectJ 2.0 compiler, using the approach you suggested.

I have a couple of questions though. The aspect project compiles to an
aspect jar, which the dependent projects weave into their own classes
during compilation. If you make changes to the aspects, is it a separate
step to tell the other projects to recompile/reweave as well? What
confused me was that I could compile the aspects fine, but when I rebuilt
the dependent projects, the aspect project would show an error on all
aspects saying that they hadn't been compiled with the "reweavable"
option. I tried passing -Xreweavable in the "non-standard compiler
options" preference, but it didn't make a difference. Anyway, I was
surprised that the aspects themselves were being rebuilt upon rebuilding
dependent projects.

Also, I wasn't able to get the visualizer to work. I know the aspects are
being applied, because I can see their results when I run in the WTE. The
visualizer just doesn't notice they're applied. In the aspectJ
preferences the "build structure model" box is selected in all projects.
I didn't see any seemingly-relevant errors in .metadata/log, nor any other
indication that things were failing. Not being able to use the visualizer
makes things difficult (which is, I'm sure, why your team built one :-).

I realize you're focusing all of your efforts into making the ajdt 1.2
series solid. Will there be any more enhancements to an environment for
Eclipse 2.1-based IDEs?

Thanks again,

Stu

Matt Chapman wrote:


> Stu, I think the approach I suggested does what you are looking for, let
> me try to expand on it a bit further. With the aspect project, you go to
> its project properties, AspectJ tab, and put in say myaspectlib.jar in the
> "output jar" field. From now on, whenever that project is built, the
> generated classes go only into this jar file (and not into the project's
> bin directory).

> Then for the projects that want to make use of this aspect library, make
> them AspectJ projects, and go to project properties, AspectJ AspectPath
> tab (as in AJDT 1.1.11 onwards), and add the myaspectlib.jar from the
> aspect project. Now whenever these projects are built, they are built with
> the AspectJ compiler, which will compile the classes in the project, and
> weave in the aspects from the aspect path, putting the output in the
> project's output directory as normal.

>> Anyway, not sure I've stated the question very clearly. In general, my
>> impression is that the documentation and examples on the ajdt site are
>> geared towards a single Eclipse project. This seems like the simple
>> case to me, and personally I haven't seen this often "in the field,"
>> rightly or wrongly.

> I agree completely, much of our focus is on getting newcomers started. I
> think we still need to continue that, but there is a rapidly growing
> number of people going beyond these first steps into more real world
> scenarios, and we certainly plan to address this area more in the near
> future. You might also like to consider writing up your own experiences so
> that others can learn from them.

> Regards,

> Matt.
Previous Topic:New AJDT demos
Next Topic:Missing error/warning indicator icons in PackageExplorer
Goto Forum:
  


Current Time: Tue Mar 19 11:24:26 GMT 2024

Powered by FUDForum. Page generated in 0.03293 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top