[ews.eclipse.technology.aspectj] Re: Status and future plans for AspectJ

["MortenCh" <nospam@xxxxxxxxx>]

"Andy Clement" <clemas@xxxxxxxxxx> wrote in message 
news:e0p4gd$hdh$1@xxxxxxxxxxxxxxxxxxxx
> And i'll take the AspectJ question.  When Eclipse 3.2 is 'complete' we 
> will upgrade AspectJ to be based on that level of the compiler.  At that 
> point we will pick up their support for jsr202 (class file format changes) 
> and jsr269 (annotation processing spec). I know support for the former is 
> already in the 3.2 milestones, but I don't think full support for jsr269 
> is (feel free to correct me if I'm wrong??).  There will be an outstanding 
> question about the class file format changes and our weaver which I've not 
> tackled yet.

First of all, thanks for the comprehensive answer!

Sounds great. I look forward to try mustang + eclipse 3.2 + aspectj out! As 
you said
there might be a problem with jsr269 (but not because of AspectJ).

> Aim for the next few days is AspectJ1.5.1 - I have one more incremental 
> compilation bug to fix before it ships.  As Matt says, the main focus 
> right now is that we want to scale up and build larger projects, in 
> shorter time and using less memory - and 1.5.1 (and accompanying AJDT) is 
> a first step towards that, requiring half the memory that 1.5.0 did under 
> Eclipse.

Sounds like a good goal.... If I can blatantly advertise for my special 
needs here,
I would like that AspectJ/AJDT offers support for multiple source/output 
folders which I
find are quite useful for java projects. I think such a feaure should be in 
line with your goal
of "scalability" as it allows the developer to better manage large/complex 
projects. As I recall
there is already some bug reports on this. Any chance we will see support 
for this ?

Cheers,
Morten Christensen