|
Ok, I have figured out
how to activate the links in the IDE, however, it is now building all of the
class files into one directory. This will not work with a j2EE project that has
EJB and Java modules that require their classes to stay within their respective
output directories. So, I proceeded to also link in the "output" directories of
these individual modules into the "master" build project. So, now I am running
into an issue in that it doesn't seem to update these directories at
all.
Has anyone created a
sample j2ee project with a Java, Web, EJB, and Aspect project? The idea is the
the aspects would reside in the Aspect project and weave into all of the other
ones. I have to hit the build button four times before I can get all weaved!!! I
have tried the master build project idea but my class files belong inside these
individual projects...
Thanks,
Ozzie
-----Original Message-----
From: Ron Bodkin
[mailto:rbodkin@xxxxxxxxxxxxxx]
Sent: Tuesday, January 13, 2004 4:42
PM
To: aspectj-users@xxxxxxxxxxx
Subject: RE:
[aspectj-users] Symbolic links for multiple module developmen
t
You can set up "linked folders" (the Eclipse term) by creating a new
folder, then checking advanced then selecting link to folder in the file
system. I'd advise creating & using a path variable like PROJECTS to
specify the source folder in other projects (so you can set up projects and
check them into CVS without hard coding your system's file paths...)
Ron Bodkin
Chief Technology Officer
New Aspects of Security
m: (415) 509-2895
------------Original Message------------
From: "Gurkan, Ozzie (MAN-Corporate)" <Ozzie.Gurkan@xxxxxxx>
To: "'aspectj-users@xxxxxxxxxxx'" <aspectj-users@xxxxxxxxxxx>
Date: Tue, Jan-13-2004 12:25 PM
Subject: RE: [aspectj-users] Symbolic links for multiple module
developmen t
I
haven't seen any symbolic link setup, so, hopefully, someone can enlighten
me on using Eclipse to fulfill both the mulitple module and incremental
builds....
I think the symbolic links in Eclipse are IDE specific and not
related to symlinks as in *nix.
Incremental compilation in ajc is a wonderfully weird thing.
Ajc will essentially "hold" all of your compiled classes in memory and
only weave those classes that need weaving upon update as opposed to
reweaving the entire class hierarchy every time you compile. IMO
it's kind of like real-time dependency checking. The downside of
this is that it's memory intensive. I'd recommend -Xmx512m for any
substantial project. The Eclipse structure view using incremental
compilation is off when doing this too. To get a 'real' view of the
weaving you have to rebuild the whole project, which could take some
time.
My $0.02(U.S.): Try ajc from the command line in both modes to get
a feel for the difference in weaving time before you dive into the Eclipse
integration.
hth,
Keith Sader
Thanks,
Ozzie
Gurkan
|
