In addition to what Matt said, the reason nifi-record is marked as provided is because it is part of nifi-standard-services-api-nar, and if your NAR was going to do anything with a record reader/writer you would have a NAR dependency on nifi-standard-services-api-nar so at runtime that is where your NAR would get nifi-record from. At build time it gets it from the provided dependency in order to compile.
On Fri, Jan 12, 2018 at 10:16 AM, Matt Gilman <matt.c.gil...@gmail.com> wrote: > Mar, > > By using a dependency like that (without the version), it must be declared > in dependencyManagement someplace. If the jar isn't being pulled into the > resulting artifact it's likely because the dependency has a scope of > provided. You can override that scope to compile when you reference it. > > Matt > > On Fri, Jan 12, 2018 at 8:34 AM, Martin Mucha <alfon...@gmail.com> wrote: > >> Hi, >> >> in nifi-standard-processors there is this dependency >> >> <dependency> >> <groupId>org.apache.nifi</groupId> >> <artifactId>nifi-record</artifactId> >> </dependency> >> >> if I just copy paste into our project some class from this bundle (to fix >> bugs) and add dependencies as mentioned one, it builds. However nifi wont >> start, because nifi-record related classes are not on classpath. >> >> What shall I do to get them on classpath? For nifi-standard-processors it's >> fine to have nifi-record as provided, but apparently for our project, >> extending the same parent, it's not. nifi-record is not provided or part of >> built nar. How to fix this? >> >> thanks, >> Mar. >>
