Scott, glad to hear you got things working. I think we've fully identified the issue around the Slack bundle but please let us know if the frontend-maven-plugin issue should resurface.
I do see how what Joe highlighted could be problematic. After doing some investigating, I've now learned that Maven treats maven.test.skip [1] and skipTests [2] differently. I hadn't considered the behavior of [1] when reviewing NIFI-5013, which introduced this possibility. Peculiarly, the dependency in nifi-slack-processors is appropriately scoped as test. I am a bit surprised to see it causing issues when both build and execution of tests is skipped. The current workaround, would be to run tests :) or at least build them with -DskipTests in lieu of -Dmaven.test.skip. Otto, had suggested doing this in a more concerted manner across the project, but I have created NIFI-5020 [3] to promote these type of test utilities to a module and then make use of that in a test scope. This is, in fact, the way that Maven prefers handling such situations as per [4]. If there are other places we have such duplication throughout the project, I would encourage folks to tag them in that ticket so we can perhaps consolidate and further reduce some duplication. --aldrin [1] https://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#skip [2] https://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#skipTests [3] https://issues.apache.org/jira/browse/NIFI-5020 [4] https://maven.apache.org/plugins/maven-jar-plugin/examples/create-test-jar.html On Mon, Mar 26, 2018 at 11:49 PM, scott <[email protected]> wrote: > Aldrin, > > That Docker image worked great for 1.5.0. When I tried to run it with the > latest master branch, however, I got the same error for > nifi-slack-processors I mentioned previously. But after reading the > response from Joe Percivall, which indicated that the slack processor step > had a test dependency, I re-ran clean again WITH tests using your Docker > image, and I finally got a complete build with the latest master. > > > Now on to building some custom processors. > > Big thanks to Aldrin and Joe for helping me get started. > > > Scott > > > > On 03/25/2018 07:32 PM, Aldrin Piri wrote: > >> Hmm, can't say I've seen those particular errors arise. >> >> I just made a simple Dockerfile as a sanity check that is available here: >> https://github.com/apiri/nifi-review-collateral/blob/master/ >> docker-build/Dockerfile >> >> A 'docker build .' against that file is all that is needed. >> >> I ran this in a couple environments successfully inclusive of an older >> laptop with Centos 7 and, the other, a more modern desktop running Debian >> 9. Could you let us know if this is also problematic? >> >> Thanks! >> >> --Aldrin >> >> On Sun, Mar 25, 2018 at 2:02 PM, scott <[email protected]> wrote: >> >> Thanks for the help Aldrin. I've tried many permutations to get this to >>> work. The two environments I've been trying to build in are Centos and >>> Ubuntu. I've tried disabling the tests and adjusting the memory, with >>> moderate success, but I still cannot get a complete compile. >>> >>> export MAVEN_OPTS="-Xms2G -Xmx8G" >>> mvn clean install -Dmaven.test.skip=true >>> >>> Env1: >>> Centos 7, Apache Maven 3.5.3, Open JDK 64bit 1.8.0_161 >>> Farthest I've gotten is nifi-web-ui >>> [ERROR] Failed to extract goal com.github.eirslett:frontend-m >>> aven-plugin:1.1:install-node-and-npm (install-node-and-npm) on project >>> nifi-web-ui: Could not extract the Node archive: >>> '/home/scotty/.m2/repository/com/github/eirslett/node/5.7.0/ >>> node-5.7.0-linux-x64.tar.gz': >>> Operation not permitted >>> >>> Env2: >>> Ubuntu 16.04 LTS, Apache Maven 3.3.9, Open JDK 64 bit 1.8.0_151 >>> Farthest I've gotten is nifi-slack-processors >>> [ERROR] Failed to execute goal on project nifi-slack-processors: Could >>> not >>> resolve dependencies for project org.apache.nifi:nifi-slack-pro >>> cessors:jar:1.6.0-SNAPSHOT: >>> Could not find artifact org.apache.nifi:nifi-standard- >>> processors:jar:tests:1.6.0-SNAPSHOT in apache.snapshots ( >>> https://repository.apache.org/snapshots) >>> >>> Thanks, >>> Scott >>> >>> >>> >>> On 03/24/2018 07:14 PM, Aldrin Piri wrote: >>> >>> Hi Scott, >>>> >>>> Are the issues with tests or something else? Could you share the >>>> error(s) >>>> you are seeing during the build process? I just checked out Travis, and >>>> it >>>> looks like we are building normally. >>>> >>>> >>>> Could you share more about your environment? >>>> >>>> "mvn -version" would be a great start as well as letting us know what >>>> distributions you attempted the build. >>>> >>>> Hopefully we can smooth out whatever is amiss and get you to those >>>> custom >>>> processors. >>>> >>>> --aldrin >>>> >>>> >>>> On Sat, Mar 24, 2018 at 9:41 PM, scott <[email protected]> wrote: >>>> >>>> Hello Devs, >>>> >>>>> I've been struggling with building NiFi's latest version. I've tried >>>>> turning off the tests, building on two different Linux instances and >>>>> different versions of Maven and Java and even gave it more memory. It >>>>> always stops somewhere in the build before completing. I'm just >>>>> wondering >>>>> if there is a secret handshake I'm missing. Is there a docker base >>>>> image, >>>>> for instance, that has an environment that will build NiFi every time? >>>>> It >>>>> takes a while to build/fail, so I'm just a bit frustrated. I'm not >>>>> really >>>>> interested in becoming a Maven expert, just want to crank out some >>>>> custom >>>>> processors. >>>>> >>>>> Thanks for your time, >>>>> >>>>> Scott >>>>> >>>>> >>>>> >>>>> >
