Niels Basjes created NIFI-8526:
----------------------------------
Summary: The maven archetype assumes to create an ASF only project.
Key: NIFI-8526
URL: https://issues.apache.org/jira/browse/NIFI-8526
Project: Apache NiFi
Issue Type: Improvement
Reporter: Niels Basjes
When I use the maven archetype to start development of a new processor I ran
into several things I propose to change.
The general problem I see is that the entire maven archetype assumes the new
project to be an ASF owned standalone project that is build with full internet
access.
This assumption is in general incorrect.
Some of the points I would like to see fixed:
1) All generated files are marked as copyright owned by the ASF. I propose to
remove all copyright notices from the new project.
2) The dependencies are pulled in via the parent project. In all scenarios I
have seen this is unacceptable. In my situations I have a library with
functionality and I want to add a maven module to my project that packages this
into a NiFi processor. I propose to have a BOM that is imported.
3) The project sometimes includes repositories that are simply not allowed with
the corporate firewalled CICD environment that needs to build the processor.
Like the (now dead) bintray that was recently fixed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
