Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [aspectj-users] Ambiguous methods with Java 8 (but not Java 7)

Hi,

Thanks for testing that on Eclipse, that helped! I think I distilled it down to a tiny example that seems to show the problem and raised a JDT bug:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=458563

Once they fix it I can fold that fix into AspectJ very quickly.

> Also, at present we compile our whole code-base with javac and then
> use the Ant task to run iajc again over the whole codebase. I wonder
> if we could just use iajc to compile those classes that actually have
> Aspects? Perhaps that might work around all/some of the compile errors
> we are getting?

If you are rebuilding everything with iajc, that does seem a duplication of effort. You either should just build with iajc or build with javac and then binary weave the aspects into what you built with iajc. This latter approach would probably avoid this bug.  So javac your java modules. ajc your aspects and supply an inpath to that ajc call that is your javac built code, the output would be the woven form of that code.

cheers,
Andy

> On Jan 27, 2015, at 2:40 AM, Adam Retter <adam.retter@xxxxxxxxxxxxxx> wrote:
> 
>> (Sometimes this is actually a bug in JDT - we could determine that by seeing if the project builds in a standard java eclipse project. If it does then it is due to the AspectJ modifications, if it doesn’t then it is a JDT bug that AspectJ is ‘inheriting’).
> 
> I just imported it as an Eclipse (Lunar) project and tried to build it
> in Eclipse with the source and target levels set to 1.8, and the
> project fails the build with the same errors as I was seeing with
> iajc. So I guess this means that it is an inherited issue? If so how
> and where should I take this, and do you want me to still raise an
> AspectJ bug?
> 
> Also, at present we compile our whole code-base with javac and then
> use the Ant task to run iajc again over the whole codebase. I wonder
> if we could just use iajc to compile those classes that actually have
> Aspects? Perhaps that might work around all/some of the compile errors
> we are getting?
> 
> Thanks Adam.
> 
> 
> -- 
> Adam Retter
> 
> skype: adam.retter
> tweet: adamretter
> http://www.adamretter.org.uk
> _______________________________________________
> aspectj-users mailing list
> aspectj-users@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/aspectj-users



Back to the top