Eclipse Groovy 插件:转换使用包含 ClassNode 条目 <List, Iterable> 的泛型作为方法 ... 直接
Eclipse Groovy Plugin: A transform used a generics containing ClassNode Entry <List, Iterable> for the method ... directly
这个应该怎么办?
protected List<BasePropCont> getChildren( boolean updCacheOn = false,
Entry< List, Iterable > _subIterEntry = null )
{
return null
// orig code removed since it seems not to matter
}
将以下内容显示为错误:
Groovy:A transform used a generics containing ClassNode
Entry <List, Iterable>
for the method
protected java.util.List getChildren(boolean updCacheOn, Entry _subIterEntry) { ... }
directly.
You are not supposed to do this. Please create a new ClassNode referring to the old
ClassNode and use the new ClassNode instead of the old one.
Otherwise the compiler will create wrong descriptors and a potential
NullPointerException in TypeResolver in the OpenJDK.
If this is not your own doing, please report this bug to the writer of the transform.
哈...解决方案是 与编辑 Save Action
一起观看 auto-handled 导入 。插件以某种方式删除了一些导入(可能处于编码时存在编译错误的状态),其中包括
import java.util.Map.Entry
:-/
手动添加解决。
其他 "disappearing" 导入已经有类似问题。
(这个奇怪错误的实际原因可能是一些(在许多已发现的)Entry
类 来自默认 Groovy 导入或在范围内)
这个应该怎么办?
protected List<BasePropCont> getChildren( boolean updCacheOn = false,
Entry< List, Iterable > _subIterEntry = null )
{
return null
// orig code removed since it seems not to matter
}
将以下内容显示为错误:
Groovy:A transform used a generics containing ClassNode
Entry <List, Iterable>
for the method
protected java.util.List getChildren(boolean updCacheOn, Entry _subIterEntry) { ... }
directly.
You are not supposed to do this. Please create a new ClassNode referring to the old ClassNode and use the new ClassNode instead of the old one.
Otherwise the compiler will create wrong descriptors and a potential NullPointerException in TypeResolver in the OpenJDK.
If this is not your own doing, please report this bug to the writer of the transform.
哈...解决方案是 与编辑 Save Action
一起观看 auto-handled 导入 。插件以某种方式删除了一些导入(可能处于编码时存在编译错误的状态),其中包括
import java.util.Map.Entry
:-/
手动添加解决。 其他 "disappearing" 导入已经有类似问题。
(这个奇怪错误的实际原因可能是一些(在许多已发现的)Entry
类 来自默认 Groovy 导入或在范围内)