[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [aspectj-users] Building just some aspects
|
If you could use maven2 instead of ant it is trivial (and in my
opinion much better)
Just drop me an email if you want help (maven that is)
/Kaare
On 28/02/06, Trasca Virgil <virgil_trasca@xxxxxxxxx> wrote:
>
> Hi,
>
> I have a project with 2 aspect files(aj files)
> and a lot of java files. I want to have 3 different
> build types. 1) build aspect 1 + java files ; 2) build
> aspect 2 + java files; 3) build just the java files
> without aspects. Can I do that? I assume it is
> possible with Ant. Do you have an example with such a
> situation? Thank you.
>
> Regards,
> Virgil
>
> --- aspectj-users-request@xxxxxxxxxxx wrote:
>
> > Send aspectj-users mailing list submissions to
> > aspectj-users@xxxxxxxxxxx
> >
> > To subscribe or unsubscribe via the World Wide Web,
> > visit
> >
> >
> https://dev.eclipse.org/mailman/listinfo/aspectj-users
> > or, via email, send a message with subject or body
> > 'help' to
> > aspectj-users-request@xxxxxxxxxxx
> >
> > You can reach the person managing the list at
> > aspectj-users-owner@xxxxxxxxxxx
> >
> > When replying, please edit your Subject line so it
> > is more specific
> > than "Re: Contents of aspectj-users digest..."
> >
> >
> > Today's Topics:
> >
> > 1. Re: [NEWSDELIVER] Scoping of weaved classes
> > per aspect in
> > aop.xml? (Matthew Webster)
> > 2. specifying @annotated traget object? (Alex
> > Shneyderman)
> >
> >
> >
> ----------------------------------------------------------------------
> >
> > Message: 1
> > Date: Mon, 27 Feb 2006 10:21:18 +0000
> > From: Matthew Webster <matthew_webster@xxxxxxxxxx>
> > Subject: [aspectj-users] Re: [NEWSDELIVER] Scoping
> > of weaved classes
> > per aspect in aop.xml?
> > To: Barry Kaplan <groups1@xxxxxxxxxxx>
> > Cc: aspectj-users@xxxxxxxxxxx
> > Message-ID:
> >
> >
> <OFCAE92E3F.EBAF33FC-ON80257122.0038AC77-80257122.0038DE9E@xxxxxxxxxx>
> > Content-Type: text/plain; charset="us-ascii"
> >
> > Barry,
> >
> > Please take a look at the load-time weaving
> > documentation:
> >
> http://www.eclipse.org/aspectj/doc/released/devguide/ltw.html.
> > You can
> > achieve what you want with the "concrete-aspect"
> > aop.xml element. You just
> > have to supply the abstract super-aspect.
> >
> > Matthew Webster
> > AOSD Project
> > Java Technology Centre, MP146
> > IBM Hursley Park, Winchester, SO21 2JN, England
> > Telephone: +44 196 2816139 (external) 246139
> > (internal)
> > Email: Matthew Webster/UK/IBM @ IBMGB,
> > matthew_webster@xxxxxxxxxx
> > http://w3.hursley.ibm.com/~websterm/
> > To: undisclosed-recipients:;
> > cc:
> > Subject: [NEWSDELIVER] Scoping of weaved
> > classes per aspect in
> > aop.xml?
> >
> >
> >
> > I would like to scope the classes considered for
> > weaving for aspects
> > defined in aop.xml.
> >
> > I have an aspect is targeting a very specific hunk
> > of code in a
> > thirdparty library, say package "com.foo.stuff..*".
> > But I also have
> > other aspects declared in aop.xml that I never want
> > to weave into
> > classes in that package.
> >
> > As far as I can tell, I can only include/exclude
> > weaving per all aspects
> > in the aop.xml. Is this correct, or is there some
> > way to say something
> > like:
> >
> > <aspectj>
> >
> > <aspects>
> > <aspect
> > name="org.opentrader.infra.foo.MyAspect>
> > <weaver>
> > <include within="foo.bar..*"/> <!--
> > for for this aspect
> > -->
> > </weaver>
> > </aspect>
> > ...
> > </aspects>
> >
> > <weaver options="-verbose -showWeaveInfo">
> > <include within="com.opentrader..*" /> <!--
> > for all aspects -->
> > <!-- Note, I never want any other aspects to
> > weave into
> > foo.bar..* -->
> > </weaver>
> >
> > </aspectj>
> >
> >
> >
> > -------------- next part --------------
> > An HTML attachment was scrubbed...
> > URL:
> >
> http://eclipse.org/pipermail/aspectj-users/attachments/20060227/41ad3295/attachment.html
> >
> > ------------------------------
> >
> > Message: 2
> > Date: Mon, 27 Feb 2006 10:55:36 -0500
> > From: "Alex Shneyderman" <a.shneyderman@xxxxxxxxx>
> > Subject: [aspectj-users] specifying @annotated
> > traget object?
> > To: aspectj-users@xxxxxxxxxxx
> > Message-ID:
> >
> >
> <693a69ba0602270755n1cbf4c6bv14f0aa56b9a24774@xxxxxxxxxxxxxx>
> > Content-Type: text/plain; charset=ISO-8859-1
> >
> > Hello, there?
> >
> > I have pretty print service that I wrote a while
> > back. Now I want that
> > service to wrap itself around all the objects that
> > have
> > @PrettyPrintable annotation. So I my aspect like
> > this:
> >
> > public aspect AnnotationBasedPrettyPrintAspect {
> >
> > protected pointcut toStringMethod (Object t) :
> > call(* (Object+).toString()) &&
> > target ((@PrettyPrintable Object)+) &&
> > !within(AnnotationBasedPrettyPrintAspect) &&
> > target(t);
> >
> > String around (Object targetObject) :
> > toStringMethod(targetObject) {
> > // do the printing magic here
> > }
> >
> > }
> >
> >
> > Is this possible? I am getting an ugly exception
> > when compiling this
> > in AJDT. If I do something like this:
> >
> > protected pointcut toStringMethod (Object t) :
> > call(* (Object+).toString()) &&
> > target (Entity+) &&
> > !within(AnnotationBasedPrettyPrintAspect) &&
> > target(t);
> >
> > it works but I really do not want to push the
> > hierarchy on client side.
> >
> > --
> > Thanks,
> > Alex.
> >
> >
> > ------------------------------
> >
> > _______________________________________________
> > aspectj-users mailing list
> > aspectj-users@xxxxxxxxxxx
> >
> https://dev.eclipse.org/mailman/listinfo/aspectj-users
> >
> >
> > End of aspectj-users Digest, Vol 12, Issue 36
> > *********************************************
> >
>
> _______________________________________________
> aspectj-users mailing list
> aspectj-users@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/aspectj-users
>
