Thanks Joe. Yes, I'm now seeing the value in separating my development from the main Nifi tree, for sure.
-----Original Message----- From: Joe Witt [mailto:[email protected]] Sent: Tuesday, September 01, 2015 3:07 AM To: [email protected] Subject: Re: Fastest way to rebuild after changing processor Rick, As Esteban pointed out -DskipTests will make the build process faster. That said, you can consider that the need to build standard procs is generally quite rare. It will surely offer a faster and more tailored experience to have a nar for your extensions unless of course you want to contribute the extensions as standard extensions to Apache NiFi. We do have maven archetypes which make creating the nar structure very simple. You can see instructions on how this works here [1]. From there the question is 'ok as I iterate how can I quickly get my new code into a build to test'? The approach I typically take is to simply run a copy command to take my new target nar and write over whatever nar I had there before in the lib directory and restart nifi. Effectively two commands. This process can be seem bulky if you are truly in a highly iterative mode of coding/deploying/tweaking/deploying. The way to often break out of such a tight cycle is to develop some effective unit tests though that isn't admittedly always very easy. Anyway hope this helps a bit. Others may have different experiences to share here for how they manage that coding/deploying cycle. Thanks Joe [1] https://cwiki.apache.org/confluence/display/NIFI/Maven+Projects+for+Extensions On Tue, Sep 1, 2015 at 3:30 AM, Esteban Aliverti <[email protected]> wrote: > If the problem is the time it takes to run all the tests, you can just > skip > them: > > mvn clean package -DskipTests > > Regards, > > > XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX > > Esteban Aliverti > - Blog @ http://ilesteban.wordpress.com > > On Tue, Sep 1, 2015 at 8:53 AM, Rick Braddy <[email protected]> wrote: > >> Hi, >> >> Is there a way to speed up rebuilding the entire Nifi source tree >> using Maven after making a minor change to a standard processor java source >> file? I mean, by-passing all the time-consuming unit tests that waste >> time during the build process and just: 1) rebuild source files that >> changed, and 2) repackage the final assembly tar.gz file so it can be >> reinstalled. >> >> I'm not real familiar yet with mvn, so hoping there's a better way to >> do quick iterative dev cycles. >> >> Thanks >> Rick >>
