or from Ant/iajc using a "tag file" which triggers a recompile when it
changes:
iterate...
------------Original Message------------
From: "Nitzan Volman" <nitzan@xxxxxxxxxxx>
To: aspectj-users@xxxxxxxxxxx
Date: Wed, May-25-2005 7:47 AM
Subject: [aspectj-users] Compiling only affected sources
Hi,
I am using AspectJ 5 M2 (iajc)
to compile a rather large project (~1500 classes).
In a typical scenario a
developer will make a minor change to a class or two - often a class that
does not have any pointcuts caught by aspects in the
projects.
Hit the "Ant run" button, and
go have a cup of coffee since the entire project is recompiled. (we do have
great coffee :) )
Upon returning he might
discover that he misplaced a semi-colon and will repeat the process: "Ant
Run" ==> go get Coffee. (Mental note: Switch to decaf
)
I realize that the aspectJ
compiler needs to process all the input since changed aspects might affect
new files,
Is there a way to speed up the
compilation process anyway?
In my case, which is quite
typical, most of the classes should not be recompiled even when aspects ARE
changed….
The Compiler should have two
stages:
The first, find out which
classes should be recompiled. The second stage should recompile only those
classes.
The goal should be a very quick
compilation when only a few classes changed…
Is this possible
today?
thanks
/Nitzan
Volman
_______________________________________________
aspectj-users mailing list
aspectj-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/aspectj-users