AW: [Hint] Recommended Parent Artifact for Custom Processor/Services projects

[Schultze, Felix]

Hi,

we found out, that creating processors with the mvn generate could lead to some 
NoClassDefFound (e.g. Jackson, etc).
In contrast to the solution in this thread, one has to use the following 
dependency in the NAR pom:

<dependency>
    <groupId>org.apache.nifi</groupId>
    <artifactId>nifi-standard-shared-nar</artifactId>
    <type>nar</type>
    <version>2.1.0</version>
</dependency>

Can you please update the mvn archetype?

Regards,
Felix

-----Ursprüngliche Nachricht-----
Von: Schultze, Felix 
Gesendet: Freitag, 17. Januar 2025 10:55
An: users@nifi.apache.org
Betreff: AW: [Hint] Recommended Parent Artifact for Custom Processor/Services 
projects

Hello,

thanks for your advice.

I just found another tutorial mentioning the "mvn archetype:generate" path.
So I put both together 😊

Parent (of generated mvn project):  org.apache.nifi:nifi-extension-bundles:2.1.0
AND dependencyMangement Import for: 
org.apache.nifi:nifi-standard-shared-bom:2.1.0:pom

Thanks,
Felix

-----Ursprüngliche Nachricht-----
Von: Bryan Bende <bbe...@gmail.com> 
Gesendet: Mittwoch, 15. Januar 2025 17:01
An: users@nifi.apache.org
Betreff: Re: [Hint] Recommended Parent Artifact for Custom Processor/Services 
projects

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 <felix.schul...@ruv.de> 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
>
>
>
>
>
>

smime.p7s
Description: S/MIME cryptographic signature