Re: the build > the mix of custom Ant tasks, macrodefs, numerous targets, etc. don't make it easy to understand.
Yes, it is a mess of obfuscation in there, which is why I've never redone it myself :) Re: the problem of building with 1.7 against a 1.8 JRE This was a known issue with ECJ which they have since fixed ( https://bugs.eclipse.org/bugs/show_bug.cgi?id=390889 ). It would be addressed by rebasing AspectJ on the ECJ version containing the fix. I will get to it soon. cheers, Andy On 14 May 2014 09:06, Frank Pavageau <frank.pavag...@gmail.com> wrote: > 2014-05-14 17:56 GMT+02:00 Jonas Trollvik <jon...@gmail.com>: > > >> However the message is still not gone. >> > That's when building with JDK 8 and source=target=1.7, right? >> >> Correct >> >> >> > It compiles fine when using -1.8 instead of -1.7. >> > >> > I already reported https://bugs.eclipse.org/bugs/show_bug.cgi?id=434118to >> > ECJ even though I stumbled upon it through AspectJ, maybe this one >> should also be reported (if it hasn't already). >> >> Thanks, this is not a show stopper for me anymore since I have set up >> jenkins now to build with the right jdk depending on which project I >> use. >> > > Yeah, it's not my use case either, so I didn't push it. And anyway, > there's probably a bug already opened against ECJ since it would mean the > 1.7 compatibility mode doesn't work when running with JDK 8. > > Frank > > _______________________________________________ > aspectj-users mailing list > aspectj-users@eclipse.org > https://dev.eclipse.org/mailman/listinfo/aspectj-users > >
_______________________________________________ aspectj-users mailing list aspectj-users@eclipse.org https://dev.eclipse.org/mailman/listinfo/aspectj-users
