Re: eliminate nifi-parent, split out nifi-nar-maven-plugin, have nifi in its own tree

+1 I think separate git repos is a great idea. One thing to clarify, too: most of the time the nifi project relies on the last nifi-nar-maven-plugin release, right? So that should be transparent for most people building the project. It would only be awkward for someone updating the maven

RE: [DISCUSS] Feature proposal: Read-only mode as default

I'm definitely a +1. I accidentally drag processors all the time when I'm panning around a large graph. I can understand how someone would get annoyed with this, though, and I can also appreciate the desire to not start storing user preferences. However, I think we should probably at least

Re: Help required with my custom controller service

All, Was this ever solved / explained? I'm having a similar issue. If there's a simple answer that I'm missing that would be great... otherwise I might post an example set of NARs somewhere tomorrow. Probably the simplest question first is, if I want to create a custom processor that uses a

Re: Instantiating a Controller Service in a Junit test

Mark Thanks for the information, it works a treat. Dave On Monday, 10 August 2015, 1:12, Mark Payne marka...@hotmail.com wrote: David, Yes, you'll also need to set the controller service in your processor. Sorry, I forgot to mention that. So after the call to

RE: Help required with my custom controller service

Brandon, I've seen this occur when I forgot to add a dependency on the ssl-context-service-api-nar in my NAR's pom. You should have something like: dependency   groupIdorg.apache.nifi/groupId   artifactIdssl-context-service-api/artifactId   version0.3.0-SNAPSHOT/version   typenar/type