RE: [aspectj-users] Repost: independently weaving against multip le jar

[Jim.Hugunin@xxxxxxxx]

1.1rc1 supports this with the -aspectpath option.  Search for that option in the readme for the details:

http://dev.eclipse.org/viewcvs/indextech.cgi/~checkout~/aspectj-home/README-11.html#BINARY_ASPECTS

Have you tried it?  This is a new feature in 1.1 and we're always interested in clear bug reports if you encounter problems.

-Jim

> -----Original Message-----
> From: Vincenz Braun [mailto:vb@xxxxxxxxx]
> Sent: Wednesday, April 02, 2003 12:25 AM
> To: aspectj-users@xxxxxxxxxxx
> Subject: [aspectj-users] Repost: independently weaving against multiple
> jars (aspect frameworks)
> 
> Sorry for reposting this. But I think this issue is really
> important for developing aspect frameworks. Otherwise the reuse
> of good aspects is very limited.
> 
> 
> Original post:
> 
> there was a problem in weaving in framework aspects independently
> (logging, quality insurance, cache etc.)
> in multiple libraries that will be used at the same time loaded by the
> same classloader in aspectj 1.0 because the weaving in
> resulted in different aspect class files. Because you can only have
> one aspect class file in the classpath. The result was often
> a NoSuchFieldException and unpredictable behaviour.
> 
> What is the status of this issue with version 1.1 and
> byte code weaving? Is it now possible to weave in
> a set of framework aspects independently to some libraries
> and have the same aspect class that can safely be used
> at runtime for all libraries?
> 
> The following example might illustrate this.
> There might be a jakarta-commons-aspect project with
> some cool stuff. Is it possible to distribute
> aspect enabled jars (with a common set of aspects) of beanutils,
> lang etc. that are independently
> created (without each other during weaving in) and use them together?
> 
> And how can one distribute a jar containing the
> class files of the aspects? Is there a way to create
> these class files alone meaning not weaving against
> some target classes so that the aspect framework can distribute binaries?
> 
> The goal is to always have the same (runtime compatible)
> aspect.class (deliverable) out of the same source file and
> the ability to create them without having targets around.
> 
> Is this possible?
> 
> Thanks,
> Vincenz
> 
> _______________________________________________
> aspectj-users mailing list
> aspectj-users@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/aspectj-users
> 
> _______________________________________________
> aspectj-users mailing list
> aspectj-users@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/aspectj-users