RE: [aspectj-users] Iajc - outjar option

["Louth, William" <william.louth@xxxxxx>]

Hi,

I have managed to introduce aspects into a properitary product server
for the purpose of tracing ( not your typical hello world tracing but
much more powerful based around components, classifications and trace
annotators, ;-) ).

The current product management are experimenting with this new feature
and have built-in support into their custom classloader to load a
particular named jar before other jars. There is also support for
patches/hotfixes. By dropping in the <trace aspects> the onsite
technical support team can restart the server for detailed diagnosis of
production issues. Similiarly they can remove the jar and disable
tracing.

The problem I have is that I want to limit the classes placed in iajc
jar so as

- not to break any possible future patches, unless of course the classes
are the traced components
- to have an image of those classes affected by the weaving which is
useful when determine patching issues
- to ease the (unfounded) worries of others with regard to the large
iajc jar file being generated

I thought it would be easy to have done that's why I asked instead of
writing an ant task to perform the diff for me. I will have a look at
the source code and possibly make an additional option available via the
command line and ant task def.

Regards,

William


-----Original Message-----
From: Jim Hugunin [mailto:lists@xxxxxxxxxxx] 
Sent: Tuesday, September 23, 2003 5:00 PM
To: aspectj-users@xxxxxxxxxxx
Subject: Re: [aspectj-users] Iajc - outjar option


Louth, William wrote:
> Is it possible to instruct the ajc compiler when using the injars and 
> outjar option to only output those classes on the classpath (task
> defined) that have been changed via the weaving process?

There's currently no tool support available for this.  Obviously, the 
weaver has this information available and this would be easy to 
implement.  Could you say more about why this feature would be useful to

you?

BTW - If you're willing to build from source, you could probably 
implement this feature for your internal purposes quite easily.  Just 
modify the method org.aspectj.weaver.bcel.BcelWeaver.dumpUnchanged to do

nothing.

Jim Hugunin -- http://hugunin.net


_______________________________________________
aspectj-users mailing list
aspectj-users@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/aspectj-users