Cool, I have setup a bug in the Groovy JIRA: https://issues.apache.org/jira/browse/GROOVY-9238
Regards, Andrew Allen On Thu, Aug 29, 2019 at 9:46 AM Paul King <pa...@asert.com.au> wrote: > Hi Andrew, > > This is a good place to ask questions. It looks like a bug to me when a > collector collects another collector. This is supposed to work and from > memory we have working cases in our test suite. I'd need to look into it a > bit further to be sure. > > @Immutable is a special case since we handle 2.4 compiled classes which > may have the original @Immutable annotation which existed prior to it being > an annotation collector. > > It would be great if you could raise an issue in Jira. > > Cheers, Paul. > > > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> > Virus-free. > www.avast.com > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> > <#m_2581449658717207293_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > > On Thu, Aug 29, 2019 at 10:30 PM Andrew Allen <andrew.st.al...@gmail.com> > wrote: > >> Hi, >> >> I'm attempting to upgrade to groovy 2.5 for a few of my projects and I'm >> running into an issue using AnnotationCollector (includes Immutable and >> CompileStatic) on a custom annotation. When using the groovy 2.4.12 >> compiler I see the expected bytecode get generated. However when compiling >> with the groovy 2.5.8 (or any groovy 2.5) compiler I'm not seeing the >> additional constructors getting created in the bytecode. >> >> Is this an expected change with the updates to the Immutable annotation? >> Is there a way to get the consistent behavior that is displayed in Groovy >> 2.4? >> >> I have an example project (https://github.com/kod4n/groovy-gradle-issue) >> that uses gradle as the build system, the issue can be verified by >> executing tests in the project with ./gradlew clean test. >> >> If there is a better place to ask this question please let me know. >> >> Thanks, >> Andrew Allen >> >
