The reason is that you want to ensure that any change triggers a build of the jar and then nar and pushes both into Nexus or whatever you're using.
On Sun, Oct 20, 2019 at 12:07 PM sanjeet rath <[email protected]> wrote: > Thanks Mike :) > > On Sun, Oct 20, 2019 at 9:34 PM Mike Thomsen <[email protected]> > wrote: > >> The pom associated with the bundle. >> >> On Sun, Oct 20, 2019 at 11:41 AM sanjeet rath <[email protected]> >> wrote: >> >>> >>> Hi Team, >>> >>> My requirement is build to custom email processor for >>> extractingBody(already code changes are done). >>> I have implemented CI in this project using jenkin. >>> >>> SO my project structure is: >>> NIFI-EMAIL-BOUNDLE >>> ->NIFI-EMAIL-PROCESSOR >>> ->NIFI-EMAIL-NAR >>> >>> So every above project has a pom file, my required expected nar file has >>> been generated in NIFI-EMAIL-NAR projects target file. >>> So in jenkin job which pom file path should be given to generate the nar >>> file. >>> >>> Thanks, >>> Sanjeet >>> >>> -- >>> Sanjeet Kumar Rath, >>> mob- +91 8777577470 >>> >>> > > -- > Sanjeet Kumar Rath, > mob- +91 8777577470 > >
