Re: [ajdt-dev] ajdt+groovy-eclipse

[Andy Clement <andrew.clement@xxxxxxxxx>]

Hi Steve,

The bug you are looking for is this one:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=287092

> Is it possible to run AJDT and Eclipse-Groovy in the same project?  Or
> rather is it possible to ever do this in the future?  Or are there
> underlying limitations of eclipse that would prevent this?

The limitations are simply that: Groovy-Eclipse patches
org.eclipse.jdt.core; AspectJ uses a branch of jdt core called
org.aspectj.org.eclipse.jdt.core.  This means when you switch your
project to AspectJ (and it switches compiler) it starts using one that
doesn't have the groovy-eclipse changes in.  And when you switch your
project back to groovy you don't have a compiler that is Aspect aware.

In theory it is just a task of taking the patches made to
org.eclipse.jdt.core and applying them to the org.aspectj copy of jdt
core - but we never find the time.

It sounds like you do want the weaver to weave into the groovy code
(rather than just using groovy for scripts which could possibly be
made to work in an easier way).  If you were able to split the
project, you could maybe get something working.  Groovy in one
project, then use 'inpath' on the AspectJ project to consume the
groovy compiled code and include it in the output of the AspectJ
project.

So we know what the challenge is, but it doesn't ever seem to reach
the top of the priority list...

cheers
Andy

On 29 February 2012 07:42, Steve Ash <stevemash@xxxxxxxxx> wrote:
>
> I looked for anything existing in the codehaus jira for groovy+eclipse as
> well as the bugzilla tracker for AJDT and didn't find anything related, even
> though I'm sure its come up before.  So I will ask, and apologize if its
> already been covered extensively.
>
> Is it possible to run AJDT and Eclipse-Groovy in the same project?  Or
> rather is it possible to ever do this in the future?  Or are there
> underlying limitations of eclipse that would prevent this?
>
> Since we do (and want to continue doing) compile time weaving-- I guess our
> best option is to use load time weaving in eclipse for junit etc and then
> use re-weaving at compile time to weave aspects into the bytecode coming out
> of eclipse-groovy compiler?
>
> For us the only aspects that we use are @Transactional and others that are
> still compilable as java code by javac -- so maven-groovy should be able to
> handle it.
>
> But this is still a pretty big departure from our current toolchain (just
> straight aspectj and AJDT) so I am hoping there is a better option or plans
> for one, since you guys are one in the same, I think.
>
> Thanks,
>
> Steve
>
>
> _______________________________________________
> ajdt-dev mailing list
> ajdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/ajdt-dev
>