You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by GitBox <gi...@apache.org> on 2019/06/12 15:08:48 UTC

[GitHub] [nifi] bbende commented on issue #3338: NIFI-5859 Modifications to extension manifest generation to better su…

bbende commented on issue #3338: NIFI-5859 Modifications to extension manifest generation to better su…
URL: https://github.com/apache/nifi/pull/3338#issuecomment-501317455
 
 
   @alecosborne Sorry for the issue... 
   
   We have a bit of a weird dependency situation where the NAR Maven plugin can't have a direct dependency on nifi-api, it can only assume that nifi-api is on the classpath of the NAR being built, but then the code for generating the manifest needs to be based on the API so it has to live in the API. 
   
   So we released a version of the manifest docs stuff in nifi-api 1.9.2, but then while continuing to work on registry 0.4.0 there were more changes needed, so we haven't yet released nifi-api 1.10.0 which would have the necessary changes.
   
   What you would have to do for now is build nifi-api from master using a 'mvn clean install', then change the dependencies in your custom NAR to use nifi-api 1.10.0-SNAPSHOT. Part of it will depend on whether your custom NAR has a parent of nifi-nar-bundles, if so then you might need your own dependencyManagement to force the version to 1.10.0-SNAPSHOT, if not then you can probably just add the version to the dependency. 
   
   https://cwiki.apache.org/confluence/display/NIFI/Maven+Projects+for+Extensions#MavenProjectsforExtensions-Inheritance
   
   We should document this somewhere though so that it is clear that the extension capabilities in registry are meant to be used with the next released version NiFi and nifi-api. I will try to think of where this makes sense to be documented.

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services