Congratulations, Peter!
On Fri, 31 May 2019 at 7:07 AM, Michael Moser wrote:
> Great work, Peter. Congrats!
>
>
> On Thu, May 30, 2019 at 8:05 PM Marc Parisi wrote:
>
> > Congrats!
> >
> > On Thu, May 30, 2019, 2:58 PM Jeff wrote:
> >
> > > Welcome to the PMC, Peter! Congrats!
> > >
> > >
Great work, Peter. Congrats!
On Thu, May 30, 2019 at 8:05 PM Marc Parisi wrote:
> Congrats!
>
> On Thu, May 30, 2019, 2:58 PM Jeff wrote:
>
> > Welcome to the PMC, Peter! Congrats!
> >
> > On Thu, May 30, 2019 at 2:45 PM Tony Kurc wrote:
> >
> > > Congratulations Peter!!
> > >
> > > On
Congrats!
On Thu, May 30, 2019, 2:58 PM Jeff wrote:
> Welcome to the PMC, Peter! Congrats!
>
> On Thu, May 30, 2019 at 2:45 PM Tony Kurc wrote:
>
> > Congratulations Peter!!
> >
> > On Thu, May 30, 2019 at 11:21 AM Aldrin Piri wrote:
> >
> > > NiFi Community,
> > >
> > > On behalf of the
Congratulations Peter!
On Thu, May 30, 2019 at 2:58 PM Jeff wrote:
> Welcome to the PMC, Peter! Congrats!
>
> On Thu, May 30, 2019 at 2:45 PM Tony Kurc wrote:
>
> > Congratulations Peter!!
> >
> > On Thu, May 30, 2019 at 11:21 AM Aldrin Piri wrote:
> >
> > > NiFi Community,
> > >
> > > On
I think the issue is you are building with the latest NAR plugin, but
then you have a dependency on an older version of nifi-api.
Not sure how your project is setup, but try changing to nifi-api
1.9.2. If you are using a project generated from the archetype, then
you may be getting nifi-api from
Welcome to the PMC, Peter! Congrats!
On Thu, May 30, 2019 at 2:45 PM Tony Kurc wrote:
> Congratulations Peter!!
>
> On Thu, May 30, 2019 at 11:21 AM Aldrin Piri wrote:
>
> > NiFi Community,
> >
> > On behalf of the Apache NiFi PMC, I am pleased to announce that Peter
> Wicks
> > has accepted
Congratulations Peter!!
On Thu, May 30, 2019 at 11:21 AM Aldrin Piri wrote:
> NiFi Community,
>
> On behalf of the Apache NiFi PMC, I am pleased to announce that Peter Wicks
> has accepted the PMC's invitation to join the Apache NiFi PMC.
>
> Peter's contributions have been plentiful in code,
Congrats, Peter! Well deserved.
On Thu, May 30, 2019 at 1:22 PM Andy LoPresto wrote:
>
> Congratulations Peter.
>
> Andy LoPresto
> alopre...@apache.org
> alopresto.apa...@gmail.com
> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69
>
> > On May 30, 2019, at 8:22 AM, Joe Witt
Hi Andy,
Thanks for bringing this up and looking into the mechanics of how to
get it working. I am a +1 for signing our maven artifacts.
Thanks,
Kevin
On Wed, May 29, 2019 at 6:09 PM Andy LoPresto wrote:
>
> Hi folks,
>
> I am writing to propose updating our release process to include signing
I am also in favor of splitting the nifi maven project up into smaller
projects with independent release cycles in order to decouple
development at well defined boundaries/interfaces and also to
facilitate code reuse.
In anticipation of eventually working towards a NiFi 2.0 that
introduces bigger
Congratulations Peter.
Andy LoPresto
alopre...@apache.org
alopresto.apa...@gmail.com
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69
> On May 30, 2019, at 8:22 AM, Joe Witt wrote:
>
> Congrats and thanks Peter!
>
> On Thu, May 30, 2019 at 11:21 AM Aldrin Piri wrote:
>
Congratulations!
On May 30, 2019 at 11:21:31, Aldrin Piri (ald...@apache.org) wrote:
NiFi Community,
On behalf of the Apache NiFi PMC, I am pleased to announce that Peter Wicks
has accepted the PMC's invitation to join the Apache NiFi PMC.
Peter's contributions have been plentiful in code,
3.5.1 is not a valid version of the NAR plugin. The current released
version used by NiFi master is 1.3.1 ...
https://github.com/apache/nifi/blob/master/pom.xml#L492
Does the same thing happen using 1.3.1?
On Thu, May 30, 2019 at 1:02 PM Russell Bateman wrote:
>
> In /pom.xml/, I have:
>
>
>
In /pom.xml/, I have:
*org.apache.nifi*
*nifi-nar-maven-plugin*
*3.5.1*
*true*
I get this, which isn't fatal, when my NAR is built. I would like
a) to know to what "extension(s)" this refers (related to the
plug-in configuration in /pom.xml/?),
b) where to put extension
I am a strong +1 on the separation and reducing the build time. With that in
mind, I think the process I brought up yesterday [1] of signing our artifacts
with GPG as part of the Maven build is paramount, because we would now be
consuming core code across multiple projects/repositories, so
In regards to "We 'could' also split out the 'nifi-api'...", NiFi 2.0 would
also be a good time to look at more clearly defining the separation between
the UI and the framework. Where nifi-api is the contract between the
extensions and the framework, the NiFi Rest api is the contract between the
In the same category of challenges that Peter pointed out, it might be
difficult for Travis to build the "framework" and "extensions" projects if
there are changes in a PR that affect both projects.
Is there a good way in Travis to have the workspace/maven repo shared
between projects in a single
yeah that is a good point. We 'could' also split out the 'nifi-api' which
is the only 'contract' between extensions and core. Not sure the juice is
worth the squeeze but then again we rarely change that thing.
On Thu, May 30, 2019 at 11:23 AM Peter Wicks (pwicks)
wrote:
> One more "not
One more "not awesome" would be that core changes that affect extensions will
be a little harder to test. If I make a core change that changes the signature
of an interface/etc... I'll need to do some extra work to make sure I don't
break extensions that use it.
Still worth it, just one more
Congrats and thanks Peter!
On Thu, May 30, 2019 at 11:21 AM Aldrin Piri wrote:
> NiFi Community,
>
> On behalf of the Apache NiFi PMC, I am pleased to announce that Peter Wicks
> has accepted the PMC's invitation to join the Apache NiFi PMC.
>
> Peter's contributions have been plentiful in
NiFi Community,
On behalf of the Apache NiFi PMC, I am pleased to announce that Peter Wicks
has accepted the PMC's invitation to join the Apache NiFi PMC.
Peter's contributions have been plentiful in code, community, reviews and
discussion after becoming a committer in November 2017. His impact
Team,
We've discussed this a bit over the years in various forms but it again
seems time to progress this topic and enough has changed I think to warrant
it.
Tensions:
1) Our build times take too long. In travis-ci for instance it takes 40
minutes when it works.
2) The number of builds we do
Hello,
This definitely sounds like the top of thing that NiFi should be pretty good
at. Can you provide more details?
What kind of problems are you running into when changing the date format? Can
you provide sample input and
desired output?
Thanks
-Mark
On May 29, 2019, at 12:11 PM, Maiuri
23 matches
Mail list logo
