Skip to content

Fluid Entity Ambiguity

Daan van Yperen edited this page Sep 13, 2016 · 2 revisions

The fluid entity plugin will always produce predictable and stable method names. Because of this it will fail early when a possibly ambiguous situation is detected. Check here for some insight how methods will be named

The plugin will show the classes, fields and/or methods causing the conflict. You can typically resolve it with a quick rename.

[ERROR] .. [public long com.artemis.Grok.clear2()] causes ambiguous method long grokClear2()
[ERROR] .. [public void com.artemis.Grok.getClear2()] causes ambiguous method com.artemis.E grokClear2()

IF the error doesn't show up in Gradle make sure gradle logging is enabled. Add --info --stacktrace to your build command.

Clone this wiki locally