[GRADLE-2682] Cross compilation of Groovy annotation on Java class does not work Created: 13/Feb/13 Updated: 10/Feb/17 Resolved: 10/Feb/17 |
|
Status: | Resolved |
Project: | Gradle |
Affects Version/s: | 1.4 |
Fix Version/s: | None |
Type: | Bug | ||
Reporter: | wujek srujek | Assignee: | Unassigned |
Resolution: | Won't Fix | Votes: | 0 |
Attachments: | annotation_test.tgz |
Description |
The project (Groovy 2.1.0, gradle 1.4) is attached to this issue. @Retention(RetentionPolicy.RUNTIME) @Target([ElementType.TYPE, ElementType.METHOD]) @interface Tx { String value() default 'def' } on this class: @Tx public class PersonServiceJava { } results in the following build failure:
My environment:
I am not sure if this is a Gradle issue, might be something in Groovy, but similar code works in groovyConsole (but the class is not a Java class)... Seems to be something in cross-compilation. |
Comments |
Comment by Peter Niederwieser [ 22/Feb/13 ] |
Looks like a Groovy stub generator bug. Here is the Java stub generated by the Groovy compiler (compileGroovy.groovyOptions.keepStubs = true): import java.lang.annotation.*; import java.lang.*; import java.io.*; import java.net.*; import java.util.*; import groovy.lang.*; import groovy.util.*; @java.lang.annotation.Retention(value=java.lang.annotation.RetentionPolicy.RUNTIME) @java.lang.annotation.Target(value={java.lang.annotation.ElementType.TYPE,java.lang.annotation.ElementType.METHOD}) public @interface Tx { java.lang.String value(); } As you can see, the default value is missing. |
Comment by wujek srujek [ 22/Feb/13 ] |
Yup, neither does it work on the command line when invoked with groovyc --jointCompilation. Have you issued it to groovy already? If not, I will do it. Thanks. |
Comment by Peter Niederwieser [ 22/Feb/13 ] |
I haven't. |
Comment by Benjamin Muschko [ 15/Nov/16 ] |
As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub. We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to. Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:
We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle! |
Comment by Benjamin Muschko [ 10/Feb/17 ] |
Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved. |