<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Creating a NiFi processor nar includes all available versions of a dependency in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Creating-a-NiFi-processor-nar-includes-all-available/m-p/179022#M73024</link>
    <description>&lt;P&gt;I'm building a custom processor (using the nifi-nar-maven-plugin plugin for assembling) and today, after updating a few dependencies, I noticed the produced nar file was almost twice of its original size.  I extracted the nar file only to find that multiple versions of dependencies were packaged, rather than just the updated ones specified in the pom file.&lt;/P&gt;&lt;P&gt;Is this a known issue?  Any solution?&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="47421-2018-01-02-13-31-48.jpg" style="width: 342px;"&gt;&lt;img src="https://community.cloudera.com/t5/image/serverpage/image-id/19430i5F7066F4AE57E3C4/image-size/medium?v=v2&amp;amp;px=400" role="button" title="47421-2018-01-02-13-31-48.jpg" alt="47421-2018-01-02-13-31-48.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
    <pubDate>Sun, 18 Aug 2019 09:26:32 GMT</pubDate>
    <dc:creator>orendain</dc:creator>
    <dc:date>2019-08-18T09:26:32Z</dc:date>
    <item>
      <title>Creating a NiFi processor nar includes all available versions of a dependency</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Creating-a-NiFi-processor-nar-includes-all-available/m-p/179022#M73024</link>
      <description>&lt;P&gt;I'm building a custom processor (using the nifi-nar-maven-plugin plugin for assembling) and today, after updating a few dependencies, I noticed the produced nar file was almost twice of its original size.  I extracted the nar file only to find that multiple versions of dependencies were packaged, rather than just the updated ones specified in the pom file.&lt;/P&gt;&lt;P&gt;Is this a known issue?  Any solution?&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="47421-2018-01-02-13-31-48.jpg" style="width: 342px;"&gt;&lt;img src="https://community.cloudera.com/t5/image/serverpage/image-id/19430i5F7066F4AE57E3C4/image-size/medium?v=v2&amp;amp;px=400" role="button" title="47421-2018-01-02-13-31-48.jpg" alt="47421-2018-01-02-13-31-48.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 18 Aug 2019 09:26:32 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Creating-a-NiFi-processor-nar-includes-all-available/m-p/179022#M73024</guid>
      <dc:creator>orendain</dc:creator>
      <dc:date>2019-08-18T09:26:32Z</dc:date>
    </item>
    <item>
      <title>Re: Creating a NiFi processor nar includes all available versions of a dependency</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Creating-a-NiFi-processor-nar-includes-all-available/m-p/179023#M73025</link>
      <description>&lt;P&gt;Turns out it was due to not calling maven's "clean" before re-packaging.  It had magically disappeared from my sbt tasks during some update.&lt;/P&gt;</description>
      <pubDate>Wed, 03 Jan 2018 06:29:07 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Creating-a-NiFi-processor-nar-includes-all-available/m-p/179023#M73025</guid>
      <dc:creator>orendain</dc:creator>
      <dc:date>2018-01-03T06:29:07Z</dc:date>
    </item>
    <item>
      <title>Re: Creating a NiFi processor nar includes all available versions of a dependency</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Creating-a-NiFi-processor-nar-includes-all-available/m-p/179024#M73026</link>
      <description>&lt;P&gt;Can anyone tell me how can we add the version numbers to our custom processors. I am trying to pass the version in my pom, like below&lt;/P&gt;&lt;P&gt;&amp;lt;version&amp;gt;2.0.0-snapshot&amp;lt;/version&amp;gt;&lt;BR /&gt;  &amp;lt;packaging&amp;gt;pom&amp;lt;/packaging&amp;gt;&lt;BR /&gt;  &amp;lt;artifactId&amp;gt;project-artifactID&amp;lt;/artifactId&amp;gt;&lt;BR /&gt; &lt;BR /&gt; &amp;lt;parent&amp;gt;&lt;BR /&gt;  &amp;lt;groupId&amp;gt;groupName&amp;lt;/groupId&amp;gt;&lt;BR /&gt;  &amp;lt;artifactId&amp;gt;parent-project-name&amp;lt;/artifactId&amp;gt;&lt;BR /&gt;  &amp;lt;version&amp;gt;1.0.0&amp;lt;/version&amp;gt;&lt;BR /&gt; &amp;lt;/parent&amp;gt;&lt;BR /&gt;&lt;BR /&gt;Basically, I'm expecting my custom processor should pick the version 2.0.0-snapshot while building but that's not happening. Can anyone point me out to the problem?&lt;/P&gt;</description>
      <pubDate>Wed, 04 Apr 2018 18:46:12 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Creating-a-NiFi-processor-nar-includes-all-available/m-p/179024#M73026</guid>
      <dc:creator>akshata_nilekan</dc:creator>
      <dc:date>2018-04-04T18:46:12Z</dc:date>
    </item>
    <item>
      <title>Re: Creating a NiFi processor nar includes all available versions of a dependency</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Creating-a-NiFi-processor-nar-includes-all-available/m-p/179025#M73027</link>
      <description>&lt;P&gt;I just iterated mine.    &lt;A href="https://github.com/tspannhw/nifi-tensorflow-processor" target="_blank"&gt;https://github.com/tspannhw/nifi-tensorflow-processor&lt;/A&gt;&lt;/P&gt;&lt;P&gt;make sure you update all the poms, one in each subdirectory.&lt;/P&gt;&lt;P&gt;also then&lt;/P&gt;&lt;P&gt;mvn clean&lt;/P&gt;&lt;P&gt;mvn package&lt;/P&gt;&lt;P&gt;make this 2 as well  &amp;lt;version&amp;gt;1.0.0&amp;lt;/version&amp;gt;&lt;/P&gt;</description>
      <pubDate>Wed, 04 Apr 2018 18:50:29 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Creating-a-NiFi-processor-nar-includes-all-available/m-p/179025#M73027</guid>
      <dc:creator>TimothySpann</dc:creator>
      <dc:date>2018-04-04T18:50:29Z</dc:date>
    </item>
    <item>
      <title>Re: Creating a NiFi processor nar includes all available versions of a dependency</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Creating-a-NiFi-processor-nar-includes-all-available/m-p/277972#M73028</link>
      <description>&lt;P&gt;I want to create three custom nifi processors say B,C,D where the common functionality is extracted to an abstract class say A which extends nifi's abstract processor and B,C,D all child of A. What is the recommended way of doing that?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 20 Sep 2019 18:37:33 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Creating-a-NiFi-processor-nar-includes-all-available/m-p/277972#M73028</guid>
      <dc:creator>Psen</dc:creator>
      <dc:date>2019-09-20T18:37:33Z</dc:date>
    </item>
  </channel>
</rss>

