You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Joseph Percivall (JIRA)" <ji...@apache.org> on 2016/12/13 14:48:58 UTC

[jira] [Resolved] (MINIFI-155) MQTT nar skipped due to warning: "Unable to resolve required dependency 'nifi-standard-services-api-nar'.

     [ https://issues.apache.org/jira/browse/MINIFI-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joseph Percivall resolved MINIFI-155.
-------------------------------------
    Resolution: Fixed
      Assignee: Joseph Percivall

While resolving MINIFI-154[1] dependencies were moved around a bit and now there is no "minifi-standard-services-api-nar" and instead we import "nifi-standard-services-api-nar" directly. This should no longer be an issue.

[1] https://issues.apache.org/jira/browse/MINIFI-154

> MQTT nar skipped due to warning: "Unable to resolve required dependency 'nifi-standard-services-api-nar'.
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: MINIFI-155
>                 URL: https://issues.apache.org/jira/browse/MINIFI-155
>             Project: Apache NiFi MiNiFi
>          Issue Type: Bug
>          Components: Core Framework
>    Affects Versions: 0.1.0
>            Reporter: Andrew Lim
>            Assignee: Joseph Percivall
>
> I wanted to run flow that used PublishMQTT, a processor not shipped with MiNiFi.
> I copied the nifi-mqtt-nar-1.1.0.nar into the MiNiFi lib directory, but when I start MiNiFi, there is a problem with the nars not liking changing "nifi-standard-services-api-nar" to "minifi-standard-services-api-nar", specifically:
> 2016-12-05 14:11:52,857 WARN [main] org.apache.nifi.nar.NarClassLoaders Unable to resolve required dependency 'nifi-standard-services-api-nar'. Skipping NAR /Users/andrewmlim/Snapshots/minifi-0.1.0/./work/nar/extensions/nifi-mqtt-nar-1.1.0-SNAPSHOT.nar-unpacked
> Workaround:  If I drop "nifi-standard-services-api-nar" into the lib dir, the flow works fine.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)