phrocker edited a comment on issue #3330: NIFI-6072: Add sub project to package nifi-minifi-jni required NARs a… URL: https://github.com/apache/nifi/pull/3330#issuecomment-466719781 > @phrocker is the main rationale to avoid needing this build and the associated tooling in cpp land? I see this is currently in a profile and I think that is okay for the common case, but do you think this would be a standard inclusion in our release process for NiFi such that the generated artifacts are readily available? @apiri The primary rationale is that we will eventually be able to create regression tests in this or a related package to avoid making releases that could break this linkage. Secondarily, the hope is that this feature appears more official by being a release artifact of Apache NiFi proper ( this feeds back into the first point ). The target could certainly live in C++, referencing the remote parent, without any issue whatsoever, but these two primary points were what I wanted to discuss. I would anticipate this breaking often without ownership in NiFi, and I know some profiles exist for various entities, so precedent seemed to exist in that aspect. Certainly open to discussion where we put this. My preference due to the risk to MiNiFi C++, and perceived less risk to NiFi is that if we don't put this here we don't put this in MINiFi C++ and instead provide it as documentation only -- or alternatively within a separate project altogether that does not tie this functionality to Apache NiFi MiNiFi C++.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
