Thank you Andrew and Andy, I was writing a reply to this thread and to admit that it is all my fault when your email came around :). I was putting the jar file to the wrong place.... Everything works as expected, of course.
Thank you all for the help. Cos On Wed, May 12, 2010 at 01:03PM, Andy Clement wrote: > Hi, > > 2010/5/12 Konstantin Boudnik <[email protected]>: > > Actually, I do have the jar file with compiled class of FooBarAspect in the > > classpath of iajc when I weave the upstream projects. Doesn't help > > apparently. > > That's why I've been jumping around with the actual source. > > You need it on the aspectpath. AspectJ hunts for aspects in > files/jars on the aspectpath, it does not hunt through files/jars on > the classpath. > > cheers, > Andy > > > > > On Wed, May 12, 2010 at 11:00AM, Andrew Eisenberg wrote: > >> Is there a reason why you are not adding the jar that contains > >> FooBarAspect onto your Aspect Path? That should be sufficient for > >> compilation/weaving purposes. I am not sure why you require the > >> source code for this. The Aspect class file should be all that is > >> required. > >> > >> 2010/5/12 Konstantin Boudnik <[email protected]>: > >> > Hello fellow AJ'ers. > >> > > >> > I believe the answer to my question is firm no, but want to double check > >> > and > >> > see if someone has a better solution. > >> > > >> > I have a project which split in a few components. One is a shared and a > >> > couple > >> > more are based on it i.e. upstream. I have some classes in all upstream > >> > components which I modify with AspectJ in the following manner: > >> > ═- declare an additional parent (an interface FooBar) for these classes > >> > ═- inject an extra functionality to all classes of type FooBar (by > >> > FooBarAspect) > >> > > >> > Now, in order to weave upstream to classes of type FooBar I need > >> > FooBarAspect > >> > to be present at the compilation time. Which means that I need either: > >> > ═- dup the file > >> > ═- have a source dependency to the shared component > >> > ═- pull the shared component's source artifact in the build > >> > time/unpack/use > >> > > >> > Now, first two options are ugly and pretty much unacceptable (for > >> > different > >> > reasons, though). The last is feasible although still non-elegant. Hence > >> > my > >> > question: can iajc use a source code directly from a jar file or it is > >> > imperative to unpack it first? From what I can see 'inpath' won't help. > >> > Any > >> > other options I might be unaware of? > >> > > >> > Thanks in advance for any ideas/hints you might be willing to share. > >> > ═Cos > >> > > >> > _______________________________________________ > >> > aspectj-users mailing list > >> > [email protected] > >> > https://dev.eclipse.org/mailman/listinfo/aspectj-users > >> > > >> > > >> _______________________________________________ > >> aspectj-users mailing list > >> [email protected] > >> https://dev.eclipse.org/mailman/listinfo/aspectj-users > > > > _______________________________________________ > > aspectj-users mailing list > > [email protected] > > https://dev.eclipse.org/mailman/listinfo/aspectj-users > > > > > _______________________________________________ > aspectj-users mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/aspectj-users
pgpNrZVbqTtrS.pgp
Description: PGP signature
_______________________________________________ aspectj-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/aspectj-users
