RE: [aspectwerkz-user] From aspectwerkz to aspectJ
<[email protected]> Tue, 19 Jul 2005 11:58:33 +0530
| Newsgroups | gmane.comp.java.aspectwerkz.user |
|---|---|
| Message-ID | <F6E660AB0AA03A44B5B0156530C23BF662F197@APAXM2102.dir.svc.accenture.com> |
Hi,
Could you explain this ?
1. Is AspectJ going to support plain java syntax ?
2. Which version of AspectJ/AJDT should I use with JDK 5 features and
eclipse 3.1?
3. Does AspectJ5 work with eclipse 3.1 ?
Mohan
-----Original Message-----
From: xudong [mailto:[email protected]]
Sent: Tuesday, June 28, 2005 4:35 PM
To: [email protected]; 'Alexandre Vasseur'
Subject: RE: [aspectwerkz-user] From aspectwerkz to aspectJ
Hi Alex,
Thanks. :)
Best wishes,
xudong
-----Original Message-----
From: Alexandre Vasseur [mailto:[email protected]]
Sent: Monday, June 27, 2005 12:31 PM
To: [email protected]
Subject: Re: [aspectwerkz-user] From aspectwerkz to aspectJ
Hi
Let me give the details:
AspectJ as available today is wether M2, wether "nightly build ie
upccoming M3".
If I assume you need the "plain java syntax" ie aspect defined with
annotation aka @AspectJ then this is part of M3. You can thus use the
nightly build, or wait M3.
The "how-to" material is still quite limited, though feature complete
from a syntax point of view is close (left aside hot deployment and some
other things).
I am planning to write some more how-to very soon.
Aside there is some work going on to better integrate AJDT (AspectJ
Eclipse
plugin) for the @Aspect syntax but again this is rather under
development.
AspectJ M3 is due mid july, final is end of the summer.
For migration I would advise to wait some more. For new needs, I would
strongly advise it as soon as M3 is out.
We will definitely make announcements and write how-to to help you in
this phases.
Alex
On 6/27/05, xudong <[email protected]> wrote:
> Hi,
>
> Now aspectwerkz has been *merged* into AspectJ, so I am wondering
> whether it is better to use AspectJ *NOW*?
>
> Thanks.
>
> Best wishes,
> xudong
>
This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.