[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [aspectj-dev] java6 apt processing
|
I saw your latest comment on the bug 252199. Unfortunately, using the
same technique in Eclipse as you use in maven (ie- staged compilation)
won't work. Eclipse relies on taking the results of compilation and
converting it into a Java model, which it uses to populate navigation,
search, content assist, etc. Eclipse has no way to reconcile both the
use of Lombok and AspectJ and does not know how to extract a model
from byte code that was manipulated by both libraries together.
On Wed, Nov 23, 2011 at 1:39 AM, Steve Ash <stevemash@xxxxxxxxx> wrote:
> Hello,
> Like a few others on the list, I went down the path of ajdt+lombok
> integration. I first got everything working through maven command line by
> following the tips of others: let javac+lombok compile java src to class
> files. Then use the inpath to do binary weaving of the lombok-ified class
> files to woven final class files. This worked really well for running maven
> through the command line. All of my lombok generated stuff showed up.
> Then I tried the same in AJDT in eclipse and no lombok stuff. I think this
> is the same problem that originally led me to go the binary weaving route --
> i.e. AJDT via iajc is not invoking the java6 annotation processor so lombok
> never runs (aspectj bug 252199):
> So (1) can I somehow configure AJDT to do the same trick as I do in maven?
> javac+lombok generate source -> class then set the inpath? Or (2) any news
> on:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=252199
> Andy mentions that he got it working in 2008-- any experimental feature we
> could enable to try it with lombok?
> Thanks,
> Steve
> _______________________________________________
> aspectj-dev mailing list
> aspectj-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/aspectj-dev
>
>
