Uploaded image for project: 'Apache NiFi'
  1. Apache NiFi
  2. NIFI-371

Need to document how one can build their own nars/extensions in terms of Maven configuration



    • Type: Improvement
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:


      Dan Bress writes:
      I started playing around building my own nar, and when I did I noticed that the nar contained a LICENSE and NOTICE file referencing ASF License 2.0 and "Copyright 2015 Apache NiFi". I take this to mean that it is saying my nar is licensed under ASF License 2.0, and copyright 2015 Apache NiFi. Am I misinterpreting this?
      If my interpretation is correct, Is there a way to override this? I imagine that not everyone who develops their own nar wants it to be licensed/copyright this way.

      Joe Witt writes:
      Did you use an apache nifi pom as the parent of your Nar? If so then you're inheriting a lot of automatic apache stuff.
      If you do not want those things for your extension then it is best to not inherit at all or to have your own parent that you do inherit from. It is possible in maven i believe to inherit by composition (depend on a pom) but i'm not really sure of the implications of that in terms of true 'inheritance'. If you have your own pom/parent pom though remember you need to add the dependency and enable extensions for the nar plugin and in the case of a nar you will want to indicate some of the things you might depend on are provided since they'll be in the parent classloaders for you.
      We also need to explain/show how best to handle pom management in the case you want to depend on a nar and its libs for things like SSL Contexts.
      We clearly need to get this documented/understood better.




            • Assignee:
              bende Bryan Bende
              joewitt Joseph Witt
            • Votes:
              0 Vote for this issue
              4 Start watching this issue


              • Created: