Re: [board report] Apache NiFi - July 2019

Russell, NIFI-5176 [1] is tracking Java 11 build compatibility for NiFi. PR-3404 [2] is a work-in-progress PR that I welcome review and testing from anyone in the community. From PR 3404, several other PRs have been extracted to prepare NiFi for Java 11 compatibility, and the JIRAs driving

Re: [EXT] [discuss] Splitting NiFi framework and extension repos and releases

I agree. It's very well thought out. One change to consider is splitting the extensions further into two separate repos. One that would serve as a standard library of sorts for other component developers and another that would include everything else. Things like the Record API would go into the

Re: [board report] Apache NiFi - July 2019

I mulled over whether it's appropriate to ask within this context. I guess I'll ask. Slap me if I have badly chosen, but where is NiFi respective to "modern" JDK versions? Is that too much detail for the audience of this periodic report? Thanks. On 7/10/19 11:15 AM, Joe Witt wrote: Team, I

Re: [EXT] [discuss] Splitting NiFi framework and extension repos and releases

Thanks Kevin, this looks really promising. Updating the link here as I think the page may have moved: https://cwiki.apache.org/confluence/display/NIFI/NiFi+Project+and+Repository+Restructuring Andy

Re: [EXT] [discuss] Splitting NiFi framework and extension repos and releases

Hi NiFi Dev Community, Jeff Storck, Bryan Bende, and I have been collaborating back and forth on a proposal for how to restructure the NiFi source code into smaller Maven projects and repositories based on the discussion that took place awhile back on this thread. I'm reviving this older thread

Re: [board report] Apache NiFi - July 2019

good catch! will fix On Wed, Jul 10, 2019, 2:08 PM John McGinn wrote: > Joe, > > Minor squabble, but, NiFi is getting setup for 1.10.0 release, not 0.10.0 > release. > > > > On Wednesday, July 10, 2019, 1:16:04 PM EDT, Joe Witt > wrote: > > Team, > > I was running late so submitted the

Re: [board report] Apache NiFi - July 2019

Joe, Minor squabble, but, NiFi is getting setup for 1.10.0 release, not 0.10.0 release. On Wednesday, July 10, 2019, 1:16:04 PM EDT, Joe Witt wrote: Team, I was running late so submitted the report already. Here is what I sent to the board for Apache NiFi July 2019 report. Great work

Re: [board report] Apache NiFi - July 2019

Thanks for taking care of this Joe. Looks great. Andy LoPresto alopre...@apache.org alopresto.apa...@gmail.com PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > On Jul 10, 2019, at 10:15 AM, Joe Witt wrote: > > Team, > > I was running late so submitted the report already.

[board report] Apache NiFi - July 2019

Team, I was running late so submitted the report already. Here is what I sent to the board for Apache NiFi July 2019 report. Great work and great progress all! ## Description: - Apache NiFi is an easy to use, powerful, and reliable system to process and distribute data. - Apache NiFi

Re: What if only 1 of 3 travis jobs fails?

If one of the builds passes, don't worry about it unless you happen to notice that for some odd reason your contribution doesn't work under one of the other language builds. On Wed, Jul 10, 2019 at 7:21 AM Lars Winderling wrote: > Dear core developers, > > I find myself often in a situation

What if only 1 of 3 travis jobs fails?

Dear core developers, I find myself often in a situation where 1 or 2 out of 3 travis jobs fail. So 1 or 2 of the jobs succeed anyway, the failing jobs only have some connection issue like failing to fetch some dependency jars. In that case I know, that the build was in pricinple successful,

Re: [DISCUSS] Apache NiFi MiNiFi C++ 0.6.1

I agree, I would not be comfortable with releasing a fix until it is properly tested, because there might well be other issues. On Tue, 9 Jul 2019 at 18:54, Marc Parisi wrote: > Good find! I'm +1 on adding that fix piggy backed on the aforementioned > test ticket. There are almost no tests on