Re: [aspectwerkz-dev] AspectWerkzC task

when doing offline weaving, we are building a classloader that will
somehow be the namespace guard for where the compilation occur and
where it does not.

the weaving engine requires a classloader anyway thru the low level API:
byte[]<weaved>  transform(String className, byte[] nonWeaved,
ClassLoader definingClassLoader)

this classloader must thus contains all dependancies of the classe(s)
that gets weaved to f.e. resolve hierarchical pointcut like
within(foo.MyInterface+) [see the "+"] etc.
for loadtime weaving this is off course the case.

for offline weaving, the classloader path needs to be build and is the
union of the classes to be weaved and their dependanciies hence -cp +
"target" entries (that comes last as args of AspectWerkzC).

Alex