You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nifi.apache.org by BRANDON DEVRIES <br...@gmail.com> on 2015/05/01 16:25:25 UTC
Re: NIFI-271 / refactored parent / checkstyle / rat / findbugs
All,
I created a ticket for this[1] and attached an initial eclipse profile. After we get some wider input, opinions, should this end up in the developer section of the website?
Brandon
[1] https://issues.apache.org/jira/browse/NIFI-568 <https://issues.apache.org/jira/browse/NIFI-568>
> On Apr 28, 2015, at 3:01 PM, Aldrin Piri <al...@gmail.com> wrote:
>
>>> created eclipse/netbeans formatting rules
Re: NIFI-271 / refactored parent / checkstyle / rat / findbugs
Posted by Mark Payne <ma...@hotmail.com>.
Thanks Joe. I'll be putting together another release in just a bit.
Thanks
-Mark
Sent from my iPhone
> On May 5, 2015, at 1:06 AM, Joe Witt <jo...@gmail.com> wrote:
>
> All,
>
> As Mark was working the release today he cited too many unstable build
> issues. I had observed it myself. Basically with checkstyle we were
> seeing false positives and false negatives. Believe it is related to
> its not yet supporting multi-threaded builds, not sure. In any event
> since we already had to move RAT into a profile I just moved
> checkstyle to be part of that profile as well. So there is a
> 'contrib-check' profile now which replaced the 'check-licenses'
> profile. This 'contrib-check' profile runs both RAT and checkstyle on
> the codebase. It should be run in a single threaded build only.
>
> The idea here then is this profile can be run as someone wishes to
> contribute, by someone performing a review, and during the release
> process to validate the items of the build are correct.
>
> This resolves: https://issues.apache.org/jira/browse/NIFI-587
>
> Thanks
> Joe
>
>> On Fri, May 1, 2015 at 10:38 AM, Joe Witt <jo...@gmail.com> wrote:
>> How about putting it in externals then kink to those from the website?
>>
>>> On May 1, 2015 7:34 AM, "Aldrin Piri" <al...@gmail.com> wrote:
>>>
>>> Brandon,
>>>
>>> Thanks for kicking this off. Yeah, that definitely seems workable. I
>>> have
>>> seen other Apache projects include such files as part of the repository in
>>> a contrib/externals folder.
>>>
>>> On Fri, May 1, 2015 at 10:25 AM, BRANDON DEVRIES
>>> <br...@gmail.com>
>>> wrote:
>>>
>>>> All,
>>>>
>>>> I created a ticket for this[1] and attached an initial eclipse profile.
>>>> After we get some wider input, opinions, should this end up in the
>>>> developer section of the website?
>>>>
>>>> Brandon
>>>>
>>>> [1] https://issues.apache.org/jira/browse/NIFI-568 <
>>>> https://issues.apache.org/jira/browse/NIFI-568>
>>>>
>>>>
>>>>> On Apr 28, 2015, at 3:01 PM, Aldrin Piri <al...@gmail.com> wrote:
>>>>>
>>>>>>> created eclipse/netbeans formatting rules
>>>>
>>>>
Re: NIFI-271 / refactored parent / checkstyle / rat / findbugs
Posted by Joe Witt <jo...@gmail.com>.
All,
As Mark was working the release today he cited too many unstable build
issues. I had observed it myself. Basically with checkstyle we were
seeing false positives and false negatives. Believe it is related to
its not yet supporting multi-threaded builds, not sure. In any event
since we already had to move RAT into a profile I just moved
checkstyle to be part of that profile as well. So there is a
'contrib-check' profile now which replaced the 'check-licenses'
profile. This 'contrib-check' profile runs both RAT and checkstyle on
the codebase. It should be run in a single threaded build only.
The idea here then is this profile can be run as someone wishes to
contribute, by someone performing a review, and during the release
process to validate the items of the build are correct.
This resolves: https://issues.apache.org/jira/browse/NIFI-587
Thanks
Joe
On Fri, May 1, 2015 at 10:38 AM, Joe Witt <jo...@gmail.com> wrote:
> How about putting it in externals then kink to those from the website?
>
> On May 1, 2015 7:34 AM, "Aldrin Piri" <al...@gmail.com> wrote:
>>
>> Brandon,
>>
>> Thanks for kicking this off. Yeah, that definitely seems workable. I
>> have
>> seen other Apache projects include such files as part of the repository in
>> a contrib/externals folder.
>>
>> On Fri, May 1, 2015 at 10:25 AM, BRANDON DEVRIES
>> <br...@gmail.com>
>> wrote:
>>
>> > All,
>> >
>> > I created a ticket for this[1] and attached an initial eclipse profile.
>> > After we get some wider input, opinions, should this end up in the
>> > developer section of the website?
>> >
>> > Brandon
>> >
>> > [1] https://issues.apache.org/jira/browse/NIFI-568 <
>> > https://issues.apache.org/jira/browse/NIFI-568>
>> >
>> >
>> > > On Apr 28, 2015, at 3:01 PM, Aldrin Piri <al...@gmail.com> wrote:
>> > >
>> > >>> created eclipse/netbeans formatting rules
>> >
>> >
Re: NIFI-271 / refactored parent / checkstyle / rat / findbugs
Posted by Joe Witt <jo...@gmail.com>.
How about putting it in externals then kink to those from the website?
On May 1, 2015 7:34 AM, "Aldrin Piri" <al...@gmail.com> wrote:
> Brandon,
>
> Thanks for kicking this off. Yeah, that definitely seems workable. I have
> seen other Apache projects include such files as part of the repository in
> a contrib/externals folder.
>
> On Fri, May 1, 2015 at 10:25 AM, BRANDON DEVRIES <
> brandon.devries@gmail.com>
> wrote:
>
> > All,
> >
> > I created a ticket for this[1] and attached an initial eclipse profile.
> > After we get some wider input, opinions, should this end up in the
> > developer section of the website?
> >
> > Brandon
> >
> > [1] https://issues.apache.org/jira/browse/NIFI-568 <
> > https://issues.apache.org/jira/browse/NIFI-568>
> >
> >
> > > On Apr 28, 2015, at 3:01 PM, Aldrin Piri <al...@gmail.com> wrote:
> > >
> > >>> created eclipse/netbeans formatting rules
> >
> >
>
Re: NIFI-271 / refactored parent / checkstyle / rat / findbugs
Posted by Aldrin Piri <al...@gmail.com>.
Brandon,
Thanks for kicking this off. Yeah, that definitely seems workable. I have
seen other Apache projects include such files as part of the repository in
a contrib/externals folder.
On Fri, May 1, 2015 at 10:25 AM, BRANDON DEVRIES <br...@gmail.com>
wrote:
> All,
>
> I created a ticket for this[1] and attached an initial eclipse profile.
> After we get some wider input, opinions, should this end up in the
> developer section of the website?
>
> Brandon
>
> [1] https://issues.apache.org/jira/browse/NIFI-568 <
> https://issues.apache.org/jira/browse/NIFI-568>
>
>
> > On Apr 28, 2015, at 3:01 PM, Aldrin Piri <al...@gmail.com> wrote:
> >
> >>> created eclipse/netbeans formatting rules
>
>
Re: NIFI-271 / refactored parent / checkstyle / rat / findbugs
Posted by Mark Payne <ma...@hotmail.com>.
Brandon,
I would vote yes, we will want the Eclipse formatter on the dev site. I
also have several Eclipse Code Templates that make writing processors
much easier that I would want to put there. Maybe some sort of
"Developer Resources" page.
Thanks
-Mark
------ Original Message ------
From: "BRANDON DEVRIES" <br...@gmail.com>
To: dev@nifi.incubator.apache.org
Sent: 5/1/2015 10:25:25 AM
Subject: Re: NIFI-271 / refactored parent / checkstyle / rat / findbugs
>All,
>
>I created a ticket for this[1] and attached an initial eclipse profile.
>After we get some wider input, opinions, should this end up in the
>developer section of the website?
>
>Brandon
>
>[1] https://issues.apache.org/jira/browse/NIFI-568
><https://issues.apache.org/jira/browse/NIFI-568>
>
>
>> On Apr 28, 2015, at 3:01 PM, Aldrin Piri <al...@gmail.com>
>>wrote:
>>
>>>> created eclipse/netbeans formatting rules
>