[
https://issues.apache.org/jira/browse/NIFI-10927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Doran updated NIFI-10927:
-------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Extensions from parent NAR found when generating extension manifest
> -------------------------------------------------------------------
>
> Key: NIFI-10927
> URL: https://issues.apache.org/jira/browse/NIFI-10927
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: Bryan Bende
> Assignee: Bryan Bende
> Priority: Minor
> Fix For: nifi-nar-maven-plugin-1.4.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> If NAR-A depends on NAR-B, and NAR-B has extension implementations, they get
> included in the manifest of NAR-A, even though we only want them in the
> manifest of NAR-B.
> This has to do with how we locate the service files in the NAR plugin, and
> NiFI has similar code that already handles this case:
> https://github.com/apache/nifi/blob/dfdd86cff7b6145a537ebb19114ca938fef35d55/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-nar-utils/src/main/java/org/apache/nifi/nar/StandardExtensionDiscoveringManager.java#L244
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
