Ambiguous method call - RunConfigurationBase.clone()

In my experience this comes from corrupt classfiles generated from Omnicore
Codeguide (they lack "bridge methods" which they claim supports 1.4 and 5.0
compatibility with generics, but violates the classfile spec). It might be a
retroweaver bug as well.

Sascha Weinreuter wrote:

What the hell is this? An IDEA error highlighting bug, an OpenAPI "bug",
a retroweaver issue or a bit of everything? The code compiles fine, but
how can I get rid of this incorrect error message?

Sascha

------------------------------------------------------------------------

Keith Lea wrote:

In my experience this comes from corrupt classfiles generated from
Omnicore Codeguide (they lack "bridge methods" which they claim supports
1.4 and 5.0 compatibility with generics, but violates the classfile
spec). It might be a retroweaver bug as well.

Hmm, since this is an issue I came across when implementing OpenAPI stuff, I don't think
this is related to Codeguide. After sleeping about this, I think it's an IDEA issue in any
case. Either the generated OpenAPI class files should be fixed or IDEA should be smart
enough to recognize that there can't possibly be two identically named methods with the
exact same signature. Since javac doesn't seem to care, IDEA shouldn't as well.

http://www.jetbrains.net/jira/browse/IDEA-5720


Sascha