Re: [aspectwerkz-user] Speeding up roundtrip

Hi

You perhaps need to see how the matching is done using
-Daspectwerkz.transform.details=true
That may help to narrow call side (call/get/set) pointcuts f.e. One
such pointcut can indeed sometime lead to parsing everry single
bytecode instruction.

Aside you may use include/exclude element in your aop.xm if you know
that some files will not be weaved at all.

AspectWerkzC does not support writing to a different location.
On the other hand you may be able to implement a wrapper that checks
for .class file timestamps to compile only modified files (then keep
track of the lastRun timestamp in some per project file)

Alex

On 6/21/05, Mattias Jiderhamn <[email protected]> wrote:
> Our application is big enough to require a few
> minutes of offline weaving on my machine, so we
> use online weaving in development. On the other
> hand, reloading the application in the web
> container using online weaving isn't much better
> (say ½-1 minute). This makes developing very
> slow, since the code-compile-test cycle has a lot of weaving overhead.
> 
> Is there any better way to do this? Can I have
> AspectWerkz weave only modified classes offline?
> If I weave the whole project and then try to
> compile in my IDE (IntelliJ), I get compiler
> errors. Could I make AspectWerkzC output the
> weaved files in a different directory, so that I
> can compile from the IDE and then have
> AspectWerkz weave the modified classes only?
> 
> Thanks in advance,
>    Mattias Jiderhamn
> 
>