Re: [aspectwerkz-user] Suggestion for AspectWerkzC

Hi
This is a good suggestion though rigth now the "does this class has
been weaved" does not surface up to AspectWerkzC offline compiler.
So I could easily "keep the timestamp" of all files, but not "keep the
timestamp of non weved class files and update the one of the other
files".
I ll have a deeper look at it (if you want to look, we need to bridge
the Context.isAdvised()  to appear in AspectWerkzPreProcessor.Output
data structure).

Alex

On 4/20/05, Chris Grindstaff <[email protected]> wrote:
> Hello,
> Thanks for creating AspectWerkzC. I have a small suggestion. When you
> write out a new jar it would be nice if you maintained the timestamps
> of files that you didn't change. This way it's much easier to
> determine what classes where touched by the compiler when looking at
> the instrumented jar(s).
> 
> Looking at the source, looks like a relatively straightforward change
> to compileJar().
> 
> You just need a transformedZe.setTime(ze.getTime()); for files that
> aren't actually changed.
> 
> Thanks again,
> Chris
> --
> Chris Grindstaff | http://gstaff.org
>