| Strategy for multi-project aspects with 1.1.4 in Eclipse 2.1? [message #584471] |
Fri, 29 October 2004 00:52 |
 Stu Robertson
Messages: 3
Registered: July 2009 |
Junior Member |
|
|
I've been able to "sorta" get this to work, and am wondering if anyone
has any ideas on a better approach.
The basic question is this: How can I cleanly setup a separate aspect
project which gets woven into a series of Web and Java projects (roughly
20). I'm willing to convert the "target" projects to have an aspect
nature, but would prefer that their compiled classes be woven in place,
in their bin directory. These projects are configured as a series of
web modules and java "project utility jars" in WSAD-speak, and it's
important that that be left unchanged.
I've been playing around with adding the aspect source directory as a
"linked directory" into each of the non-aspect-containing projects.
This works, but 1) causes the aspects to appear in each and every
project's compile target dir, and 2) ajdt gets understandably confused.
Another approach is discussed at
http://dev.eclipse.org/mhonarc/lists/ajdt-dev/msg00324.html and Mike was
kind enough to send along his build file for it. But drawbacks seem to
be that 1) because the weaving is done outside of ajdt, the visualizer
and annotations don't work properly and 2) it doesn't seem to place
classes in the right package structure.
I'm stumbling around on this, so if anyone has any hard-earned wisdom to
share, or even just a link, I'd really appreciate it.
Thanks,
Stu
|
|
|
Powered by
FUDForum. Page generated in 0.03391 seconds
] 
Search
Help
Register
Login
Home
