mattyb149 commented on PR #35: URL: https://github.com/apache/nifi-maven/pull/35#issuecomment-1767342297
+1 on this PR from me, I can merge unless @nandorsoma wants to :) @nicoloboschi is this the only feature of NiFi that LangStream uses? For LangStream and Pulsar, is it the metadata and/or approach to classloader isolation that makes the NAR format useful? If so I definitely think we should we refactor this to be a generic "extension packager" or something and publish it as such (as @nandorsoma suggested), and we can add NiFi-specific stuff for the NiFi plugin and publish that too. If we want to get fancy we can accept extensions for doc generation (so it's not NiFi-specific) and even the supported annotations (to make it even more flexible). That's quite a bit of work though, I'd tackle it in my spare time but that's pretty sparse these days. Would be happy to review a "Feature Proposal" on the [wiki](https://cwiki.apache.org/confluence/display/NIFI/NiFi+Feature+Proposals) if someone wanted to put up a requirements and/or design document. For the "different context" to which Soma is referring, stay tuned and keep an eye on that Feature Proposals page ;) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
