Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [aspectj-users] Can non-weaved classes be removed from generated jar after ctw

Hi Hemal,
could it be that your aspects are in reality matching much more classes than you expect them to?
So, non weaved classes are in reality partially weaved?

You could activate the debug output of the weaver to see what it's doing and eventually post here the pointcut expression that is causing unwanted weaving and see if there is a way to write it so that it targets only the right classes.

Simone

Hemal Pandya wrote:
Hello everyone,

After my trouble with load time weaving I have shifted to compile team
weaving and got it work after some trouble. This creates a huge jar,
while I have actually put advices in a few classes.

I am wondering if it would be ok to strip the non-weaved classes after
ctw and put that jar in the front of classpath. That would make it
easier for me to supply small files that can be deployed to get
AspectJ runs.

Or maybe there is already an iajc parameter that creates a jar only of
the weaved classes?

Appreciate any comments. Thanks in advance,

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


--
Simone Gianni            CEO Semeru s.r.l.           Apache Committer
http://www.simonegianni.it/



Back to the top