You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@netbeans.apache.org by Jan Lahoda <la...@gmail.com> on 2017/09/12 11:48:35 UTC
Adding Apache Rat to NetBeans build
Yesterday, I was experimenting with a patch to include the Rat tool to the
NetBeans build. Any opinion on whether it would be useful to push that (to
help us track progress with changing the headers)? Currently it would be
integrated in a very rudimentary way, with very limited excludes (like .git
and limited build artifacts).
Feedback is welcome.
Thanks,
Jan
Re: Adding Apache Rat to NetBeans build
Posted by Geertjan Wielenga <ge...@googlemail.com>.
Sounds like there's no objections, can't imagine why there would be
objections, let's do it.
Gj
On Tue, 12 Sep 2017 at 16:01, Jaroslav Tulach <ja...@oracle.com>
wrote:
> On úterý 12. září 2017 13:56:27 CEST Geertjan Wielenga wrote:
> > I think that would be great -- getting automated reports, i.e., hooked
> into
> > Jenkins, would be great too.
>
> +1 doing some work (re-licensing) without measuring progress isn't
> engineering
>
> Integrate rat in next commit and let's change
> https://builds.apache.org/job/incubator-netbeans-linux/
> to run it, archive the output file and possibly even have a graph showing
> the
> size of the reported violations. It will be motivating to see how steadily
> it
> goes down to zero.
>
> -jt
>
>
Re: Adding Apache Rat to NetBeans build
Posted by Jaroslav Tulach <ja...@oracle.com>.
On úterý 12. září 2017 13:56:27 CEST Geertjan Wielenga wrote:
> I think that would be great -- getting automated reports, i.e., hooked into
> Jenkins, would be great too.
+1 doing some work (re-licensing) without measuring progress isn't engineering
Integrate rat in next commit and let's change
https://builds.apache.org/job/incubator-netbeans-linux/
to run it, archive the output file and possibly even have a graph showing the
size of the reported violations. It will be motivating to see how steadily it
goes down to zero.
-jt
Re: Adding Apache Rat to NetBeans build
Posted by Geertjan Wielenga <ge...@googlemail.com>.
I think that would be great -- getting automated reports, i.e., hooked into
Jenkins, would be great too.
Gj
On Tue, Sep 12, 2017 at 1:48 PM, Jan Lahoda <la...@gmail.com> wrote:
> Yesterday, I was experimenting with a patch to include the Rat tool to the
> NetBeans build. Any opinion on whether it would be useful to push that (to
> help us track progress with changing the headers)? Currently it would be
> integrated in a very rudimentary way, with very limited excludes (like .git
> and limited build artifacts).
>
> Feedback is welcome.
>
> Thanks,
> Jan
>
Re: Adding Apache Rat to NetBeans build
Posted by Geertjan Wielenga <ge...@googlemail.com>.
Looking forward to typing 'ant rat' on the command line, to build NetBeans
and produce Rat output...
Gj
On Tue, 12 Sep 2017 at 19:06, Emilian Bold <em...@gmail.com> wrote:
> I didn't find Rat a very flexible tool when I looked into it.
>
> I wouldn't want it to run for every build.
>
> Sure, if we have a flag for it, it would be nice to have it in there.
>
> --emi
>
>
> On Tue, Sep 12, 2017 at 2:48 PM, Jan Lahoda <la...@gmail.com> wrote:
> > Yesterday, I was experimenting with a patch to include the Rat tool to
> the
> > NetBeans build. Any opinion on whether it would be useful to push that
> (to
> > help us track progress with changing the headers)? Currently it would be
> > integrated in a very rudimentary way, with very limited excludes (like
> .git
> > and limited build artifacts).
> >
> > Feedback is welcome.
> >
> > Thanks,
> > Jan
>
Re: Adding Apache Rat to NetBeans build
Posted by Emilian Bold <em...@gmail.com>.
I didn't find Rat a very flexible tool when I looked into it.
I wouldn't want it to run for every build.
Sure, if we have a flag for it, it would be nice to have it in there.
--emi
On Tue, Sep 12, 2017 at 2:48 PM, Jan Lahoda <la...@gmail.com> wrote:
> Yesterday, I was experimenting with a patch to include the Rat tool to the
> NetBeans build. Any opinion on whether it would be useful to push that (to
> help us track progress with changing the headers)? Currently it would be
> integrated in a very rudimentary way, with very limited excludes (like .git
> and limited build artifacts).
>
> Feedback is welcome.
>
> Thanks,
> Jan