Hello,
I think the recommended approach for most cases would be to depend on
the nifi-standard-shared-nar as the parent of your NAR.
You can import the bom for that NAR so that your processors / services
have compile time access to all the dependencies provided by this
NAR...
In the root pom of your bundle you would have:
<dependencyManagement>
<dependencies>
<dependency>
<groupId>org.apache.nifi</groupId>
<artifactId>nifi-standard-shared-bom</artifactId>
<version>${org.apache.nifi.version}</version>
<scope>import</scope>
<type>pom</type>
</dependency>
</dependencies>
</dependencyManagement>
And then your NAR pom would have a NAR dependency on the shared NAR:
<dependency>
<groupId>org.apache.nifi</groupId>
<artifactId>nifi-standard-shared-nar</artifactId>
<version>${org.apache.nifi.version}</version>
<type>nar</type>
</dependency>
Thanks,
Bryan
On Wed, Jan 15, 2025 at 8:30 AM Schultze, Felix <[email protected]> wrote:
>
> Hi,
>
>
>
> during the NIFI-2.0.0-MX phase, we set up our initial NiFi infrastructure
> with first implementations for custom-processors and
> custom-controller-services.
>
> The pom of these projects inherit from
> org.apache.nifi:nifi-nar-bundles:2.0.0-M2
>
>
>
> What artifact do you recommend now? E.g. nifi-extensions-bom ?
>
> Or can you provide the correct location in the docs? I just find “Custom
> Processor UIs”
>
>
>
> Kind regards,
>
> Felix Schultze
>
>
>
>
>
>
