[aspectj-dev] "noweave" use case

[Ramnivas Laddad <ramnivas@xxxxxxxxx>]

Hello,

I think I have a use case that cannot be implemented
(at least elegantly, anyway) without noweave/XnoWeave
option (and thus I request to make it a regular option 
instead of experimental -X).

Basically, I want to have my tracing.jar (
contains tracing aspect) weave into transaction.jar 
(contains abstract transaction mangement aspects, 
concrete policy enforcement aspects, and supporting 
classes). Assume app.jar contain business classes 
and interfaces. Each of the jar is created using
-ourjar (but not -noweave or -XnoWeave).

To build the final system I issue the following 
command:
> ajc -injars app.jar;transaction.jar 
      -aspectpath transaction.jar;tracing.jar

Now compiler gives me error due to multiply woven 
classes and aspects in transaction.jar.

Everything works fine if I create the original jar 
files using -noweave.

I could workaround by creating multiple jars, but 
I hink -noweave is the right approach as 
I really don't want to ship multiple jars that are 
needed to implement a single concern and expect the 
users to correctly specify jar files in -injars 
and -aspectpath.

-Ramnivas

__________________________________________________
Do you Yahoo!?
Yahoo! Tax Center - File online, calculators, forms, and more
http://tax.yahoo.com