[
https://issues.apache.org/jira/browse/NIFI-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14597056#comment-14597056
]
Bryan Bende commented on NIFI-371:
----------------------------------
[~danbress] [~joewitt] I started a Wiki page on creating Maven projects for
custom processors:
https://cwiki.apache.org/confluence/display/NIFI/Maven+Projects+for+Custom+Processors
It is a rough first pass, but if we iterate on it we can probably close this
ticket. I attempted to explain the issue of inheriting from nifi-nar-bundles,
and how to remove that inheritance if desired. Let me know if that part doesn't
seem right.
Any thoughts on what to add for Joe's comment about "how best to handle pom
management in the case you want to depend on a nar and its libs for things like
SSL contexts"? Is there an example you are thinking of?
> Need to document how one can build their own nars/extensions in terms of
> Maven configuration
> --------------------------------------------------------------------------------------------
>
> Key: NIFI-371
> URL: https://issues.apache.org/jira/browse/NIFI-371
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Documentation & Website
> Reporter: Joseph Witt
> Priority: Minor
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
