They're the same in name only. The N of the NiFi nars is for "NiFi" versus "native". I don't have a canned concise description, perhaps someone else will weigh in, but they are for packing together code with dependent libraries, and allowing different bundles to have different dependencies. They are similar in ilk to the concept of wars. Two wars may have different versions, potentially conflicting versions of libraries. However, tomcat, for example, can load the two web applications just fine.
On Sun, Dec 14, 2014 at 2:58 PM, Karl Heinz Marbaise <[email protected]> wrote: > > Hi Benson, > > I thought also about the nar-maven-plugin (github) just related by the > name... but i think this plugin goes a different direction but you might > better know than i do... > > The nar-maven-plugin (github) is intended to support building > (C/C++/Fortran) etc. with packaging the header files etc. into a archive > (NAR ;-)..which will be unpacked...(you know better than i do)... > > > On 12/14/14 8:41 PM, Benson Margulies wrote: > >> I'm a tiny bit active in the nar plugin on github. Do you have a fork of >> it? Are you interested in selling your fork back to the current >> maintainers? >> >> > From my point of view it does not look like this cause the code is at the > moment very rudimentary....... > > May be others in the project can say more about the nar-maven-plugin which > intention is behind it? > > > Kind regards > Karl Heinz marbaise >
