Hi Kishore,

I didn't mean to work on PR as I don't know Groovy code base that well.
So please, take over :-) If you don't mind, please submit back PR link so that 
I can learn something :-)

Tnx
Damir
On 9 Nov 2020, 14:10 +0100, Kishore Kumar <mvkishoreku...@gmail.com>, wrote:
> Hi Damir,
>   If you are not  submitting PR for this issue, I am interested in doing it. 
> Let me know if you are handling it already.
>
> Thanks,
> Kishore
>
> On 2020/10/08 18:46:37, Damir Murat <d...@gmail.com> wrote:
> > Here is reported issue: https://issues.apache.org/jira/browse/GROOVY-9772>
> >
> > Tnx,>
> > Damir>
> > On 8 Oct 2020, 14:40 +0200, Paul King <pa...@asert.com.au>, wrote:>
> > > That seems a reasonable suggestion to me. The constructor and some of the 
> > > methods of the helper class are already marked with @Generated but I see 
> > > no reason not to mark the class. Please create an issue (and PR if you 
> > > like). It might actually be a good candidate to mark also as POJO but 
> > > let's keep that separate for now.>
> > >>
> > > Cheers, Paul.>
> > >>
> > >>
> > > > On Thu, Oct 8, 2020 at 8:44 PM Damir Murat <da...@gmail.com> wrote:>
> > > > > AnnotationCollectorTransform generates an inner helper class 
> > > > > CollectorHelper with a method value().>
> > > > > Since it is not marked with @Generated, the value() method pops up in 
> > > > > the JaCoCo coverage report.>
> > > > >>
> > > > > Is it possible to mark the value() method, or whole inner helper 
> > > > > class, with @Generated?>
> > > > >>
> > > > > Tnx,>
> > > > > Damir>
> >

Reply via email to