Hi, A while back I created a Nifi processor using the provided maven archetype and this was in my experience needlessly hard.
The biggest hurdles I had essentially boil down to the archetype assuming the project being a standalone ASF project. The points I ran into: - The dependencies are pulled from an apache parent pom. Making it very hard to use it as a (new) module in an existing project. - All files are marked with a license that the created project is owned by the ASF. Which I expect to be only true in a limited number of cases. - In some cases the maven repositories are configured which are very likely to be incompatible with a corporate CICD environment (which are usually very restricted). So to improve on this I have put up a jira ticket and an initial patch to illustrate what I think the archetype should look like. https://issues.apache.org/jira/browse/NIFI-8526 https://github.com/apache/nifi/pull/5063 Since my approach includes the introduction of a nifi maven bom that is to be included by other projects I really would like your input on this. Do you agree that the issues I experienced require fixing? Do you agree with my approach? Or can what I ran into be fixed in a different way? What dependencies should / should not be part of the bom? My current patch contains only what I currently understand should be in there. Looking forward to your feedback. NIels Basjes PS Some of the processors I wrote: https://yauaa.basjes.nl/UDF-ApacheNifi.html https://dsmr.basjes.nl/#apache-minifi-processors -- Best regards / Met vriendelijke groeten, Niels Basjes
