[GROOVY-5256] Wrong generation of stubs with Generics

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.8.5
• Fix Version/s: 2.0-beta-3, 1.8.7
• Component/s: Stub generator / Joint compiler
• Environment: Windows XP 5.1.2600, JDK 1.6.0_21, Groovy 1.8.5
• Assignee: Paul King
• Reporter: Dmytro Rud
• Created: 19/Jan/12 04:27
• Updated: 13/May/12 03:30
• Resolved: 13/Feb/12 05:09

Description

When a Groovy class uses generics and is based on classes from other modules which use generics as well, the compiler generates wrong method signatures in the stub. When all classes are located in the same module, the stub is generated correctly.

The attached archive contains a Maven2 project with two sub-modules, where module2 contains a Groovy class and depends on module1. During mvn clean install, a Groovy stub with the following constructor declaration is generated in module2/target:

public Hl7v3ContinuationAwareProducer
(module1.cont.Hl7v3ContinuationAwareEndpoint endpoint, module1.core.JaxWsClientFactory clientFactory) {
super ((module1.core.AbstractWsEndpoint<ComponentType extends module1.core.AbstractWsComponent<java.lang.Object extends java.lang.Object>>)null, (module1.core.JaxWsClientFactory)null, (java.lang.Class<InType>)null, (java.lang.Class<OutType>)null);
}