Re: Build failure on macOS

Mark, Thanks for highlighting this issue. I have not seen any automated build issues on GitHub, but that appears to be running macOS 11.6.2. I noticed littleshoot 1.1.2 includes a build profile for Netty 4.1. In light of the fact that this works on Linux and other versions of macOS, I wonder

Build failure on macOS

Is anyone else having trouble building NiFi (main) on macOS? I recently upgraded to macOS Monterey 12.1 and since then I have not been able to build NiFi. I'm not sure if the failure started exactly coincidental with the macOS upgrade, but it stands out as a significant recent change. I get an

Re: BUILD FAILURE for nifi-registry-web-docs

arget\classes [INFO] ---- [INFO] BUILD FAILURE [INFO] [INFO] Total time: 3.303 s [INFO] Finished at: 2022-01-10T1

RE: Re: BUILD FAILURE for nifi-registry-web-docs

] Using 'UTF-8' encoding to copy filtered resources. > > [INFO] Copying 0 resource > > [INFO] Copying 3 resources > > [INFO] > > [INFO] --- maven-compiler-plugin:3.8.1:compile (default-compile) @ > > nifi-registry-web-docs --- > > [INFO] Changes detected - reco

Re: BUILD FAILURE for nifi-registry-web-docs

mpiling 1 source file to > D:\zhangle29\project\nifi\nifi-registry\nifi-registry-core\nifi-registry-web-docs\target\classes > [INFO] > > [INFO] BUILD FAILURE > [INFO] >

BUILD FAILURE for nifi-registry-web-docs

cs\target\classes [INFO] ---- [INFO] BUILD FAILURE [INFO] [INFO] Total time: 3.303 s [INFO] Finished at: 2022-01-10T10:22:35+08

Re: Build failure

Did you run `mvn clean install` or just have an IDE do whatever it considers a build to be after importing the Maven POMs? On Fri, Oct 1, 2021 at 11:11 AM tobin wrote: > > Hi, > > I'm trying to build NiFi for the first time. > > The build completes but when I browse to

Build failure

Hi, I'm trying to build NiFi for the first time. The build completes but when I browse to https://127.0.0.1:8443/nifi/ the page doesn't finish loading. Inspecting the page shows a lot of missing resources such as jquery libraries. All the missing items come from the nifi/assets Which module in

Re: Build Failure for project nifi-toolkit-cli

I was able to resolve cli toolkit issue by mvn clean and git clean -fxd. Then while building on windows got error on https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-runtime/src/test/groovy/org/apache/nifi/NiFiGroovyTest.groovy was able to

Re: Build Failure for project nifi-toolkit-cli

maven command -- *mvn -T 4.0C clean install*Below is the maven command line > info and errors*: - > [INFO] > > [INFO] BUILD FAILURE > [INFO] > --

Build Failure for project nifi-toolkit-cli

r VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0 maven command -- *mvn -T 4.0C clean install*Below is the maven command line info and errors*: - [INFO] ---------

PR AppVeyor build failure

It appears the AppVeyor build failed on my PR [1]. It also appears that it simply timed out after 90 minutes. Is there a way to re-run this check? [1] https://github.com/apache/nifi/pull/2703 Thanks, Mark

Re: Maven Build Failure

Aldrin After successfully created the package , and added it to the parcel in CDH distribution , am unable to download the jar file . am getting below error Error for parcel NIFI-0.0.5.nifi.p0.5-el7 : Parcel not available for OS Distribution RHEL7. Datta -- Sent from:

NiFi 1.6 build failure nifi-web-ui

Hi, I am trying to build NiFi from source but the build fails with the below error. Can anyone help me with this? Sorry if it's a newbie question. I am new to the NiFi development world. Thanks [INFO] [INFO] BUILD FAILURE

Re: Maven Build Failure

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

Re: Maven Build Failure

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

Re: Maven Build Failure

I ran into the second error today after wiping my m2 directory and running a parallel build skipping tests. Looking at the maven pom, I believe it is because "nifi-slack-processors" has a test dependency on "nifi-standard-processors". If you build the "nifi-standard-processors" first, it should

Re: Maven Build Failure

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

Re: Maven Build Failure

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

Re: Maven Build Failure

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

Maven Build Failure

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

Re: build failure

Hi Mark, Not sure of the exact cause, but I believe others were running into this issue and it was remedied by the work in https://github.com/apache/nifi/pull/2273. On Thu, Nov 16, 2017 at 9:46 PM, Mark Bean wrote: > I'm getting build failures when I attempt to build the

build failure

I'm getting build failures when I attempt to build the latest master on one environment but not another. The failure was on macOS 10.12.6, maven 3.3.9, java 1.8.0_74. I agree, some of those could (and will be soon) updated. Yet, I was able to build successfully on an AWS EC platform earlier

Re: Build failure on Mac OS X with DS_STORE files

Thank you guys! On February 11, 2017 at 16:44:12, Koji Kawamura (ijokaruma...@gmail.com) wrote: Thank you, Aldrin! Koji On Feb 12, 2017 4:42 AM, "Aldrin Piri" wrote: Koji, Just as a side note, you must perform a separate grunt deploy from the nifi-site repository for

Re: Build failure on Mac OS X with DS_STORE files

Thank you, Aldrin! Koji On Feb 12, 2017 4:42 AM, "Aldrin Piri" wrote: Koji, Just as a side note, you must perform a separate grunt deploy from the nifi-site repository for those changes to show up on the site. I took care of deploying so they would sync and they seem to

Re: Build failure on Mac OS X with DS_STORE files

Koji, Just as a side note, you must perform a separate grunt deploy from the nifi-site repository for those changes to show up on the site. I took care of deploying so they would sync and they seem to be live. --aldrin On Fri, Feb 10, 2017 at 7:43 PM, Koji Kawamura

Re: Build failure on Mac OS X with DS_STORE files

Thanks Otto, I reviewed pr1497 and merged it. For the getting started page, I assume you were referring this quick start. https://nifi.apache.org/quickstart.html I've modified the Java 8 version description as follows: "You need a recent Java 8 (or newer) JDK for the 1.x NiFi line. Older Java 8

Re: Build failure on Mac OS X with DS_STORE files

https://github.com/apache/nifi/pull/1497 On February 9, 2017 at 09:19:21, Koji Kawamura (ijokaruma...@gmail.com) wrote: Thanks! Please ping me when the PR is ready. On Thu, Feb 9, 2017 at 11:15 PM, Otto Fowler wrote: > Sure - I see what you mean, that is a much better

Re: Build failure on Mac OS X with DS_STORE files

OK - I can build with the latest JDK ( except for the DS_Store issue. So the problem is that the getting started page should not just say Java 8, is should have some version of the JDK that will actually build. On February 9, 2017 at 19:34:31, Otto Fowler (ottobackwa...@gmail.com) wrote: I am

Re: Build failure on Mac OS X with DS_STORE files

I am using 1.8.0_31 I have been able to get a complete good build, but I had to make a few changes. On February 9, 2017 at 18:34:48, Koji Kawamura (ijokaruma...@gmail.com) wrote: Hi Otto, Which version of Java are you using? I remember early version of Java 8 fails to pass the test. Would you

Re: Build failure on Mac OS X with DS_STORE files

Hi Otto, Which version of Java are you using? I remember early version of Java 8 fails to pass the test. Would you try to update JDK version and build it again? Thanks, Koji On Fri, Feb 10, 2017 at 3:43 AM, Otto Fowler wrote: > OK, that is good. There very well could

Re: Build failure on Mac OS X with DS_STORE files

OK, that is good. There very well could be something ‘special’ about what I am seeing. I am fixing things as I find them. The things that are not working make sense to me, in other words I’m not sure how they are not broken for everyone. Maybe if I get to the end of it, I’ll post what the

Re: Build failure on Mac OS X with DS_STORE files

Otto, I regularly build on a Mac without problems, and I believe a lot of contributors do as well. I haven't run into the .DS_Store issues with NiFi, probably because I rarely use Finder to access my build folders. I don't recall any issues with ScriptingProcessor, but it's been a week or more

Re: Build failure on Mac OS X with DS_STORE files

So, I could have a pr that fixes that problem, but I’m seeing new problems now. I can submit the pr then keep looking at the other problems ( meaning I can submit a pr without having a working complete build, just fixing that test ), but I’m not sure how you all handle things like this. I have

Re: Build failure on Mac OS X with DS_STORE files

Thanks! Please ping me when the PR is ready. On Thu, Feb 9, 2017 at 11:15 PM, Otto Fowler wrote: > Sure - I see what you mean, that is a much better approach. > I will certainly do that. > > > > On February 9, 2017 at 09:02:05, Koji Kawamura (ijokaruma...@gmail.com) >

Re: Build failure on Mac OS X with DS_STORE files

Sure - I see what you mean, that is a much better approach. I will certainly do that. On February 9, 2017 at 09:02:05, Koji Kawamura (ijokaruma...@gmail.com) wrote: Hi Otto, Thanks for reporting this. I personally haven't encountered this issue, but as described here [1], when I opened the

Re: Build failure on Mac OS X with DS_STORE files

Hi Otto, Thanks for reporting this. I personally haven't encountered this issue, but as described here [1], when I opened the directory that the test uses by Mac Finder application, and changed view as icon and move the icon position, then a .DS_Store file was created. I agree with your

Re: Build failure on Mac OS X with DS_STORE files

If it turns out that this *is* something you would like addressed, I can do the jira and the PR On February 8, 2017 at 23:13:16, Otto Fowler (ottobackwa...@gmail.com) wrote: @Test public void testGetURLsForClasspathWithDirectory() throws MalformedURLException { final String jarFilePath =

Re: Build failure on Mac OS X with DS_STORE files

@Test public void testGetURLsForClasspathWithDirectory() throws MalformedURLException { final String jarFilePath = "src/test/resources/TestClassLoaderUtils"; URL[] urls = ClassLoaderUtils.getURLsForClasspath(jarFilePath, (dir,name)->name.compareTo(".DS_Store") == 0, false);

Build failure on Mac OS X with DS_STORE files

Hi, I’m trying to build master on Mac OS X, following the instructions from the site linked in the README.md. My build is failing because the unit test: testGetURLsForClasspathWithDirectory in TestClassLoaderUtils. It is trying to URLs from a directory, and is expecting 2, but gets 3, because

Re: Master build failure with nifi-jolt-transform-json-ui?

gt; wrote: > > > > Trying to open that in a browser gives the same error and says no healthy > backends, maybe the npm registry is having issues? > > Thanks, > Bryan > > > On Fri, Oct 21, 2016 at 10:02 AM, Joe Gresock <jgres...@gmail.com> wrote: > > > Is

Re: Master build failure with nifi-jolt-transform-json-ui?

ne else getting a build failure on master? > > [WARNING] npm WARN package.json nifi-jolt-transform-json-ui@ No README > data > [ERROR] npm http GET > https://registry.npmjs.org/angular-ui-codemirror/-/ > angular-ui-codemirror-0.3.0.tgz > [ERROR] npm http 503 > https://r

Re: Master build failure with nifi-jolt-transform-json-ui?

Trying to open that in a browser gives the same error and says no healthy backends, maybe the npm registry is having issues? Thanks, Bryan On Fri, Oct 21, 2016 at 10:02 AM, Joe Gresock <jgres...@gmail.com> wrote: > Is anyone else getting a build failure on master? > > [WA

Master build failure with nifi-jolt-transform-json-ui?

Is anyone else getting a build failure on master? [WARNING] npm WARN package.json nifi-jolt-transform-json-ui@ No README data [ERROR] npm http GET https://registry.npmjs.org/angular-ui-codemirror/-/angular-ui-codemirror-0.3.0.tgz [ERROR] npm http 503 https://registry.npmjs.org/angular-ui

Re: NiFi 1.0.0 build failure in netbeans

Hi below is the error: BUILD FAILURE Total time: 16.588 s Finished at: 2016-10-18T15:40:30+05:30 Final Memory: 39M/673M

Re: NiFi 1.0.0 build failure in netbeans

essor-bundle-archetype SKIPPED > nifi-service-bundle-archetype .. SKIPPED > nifi-external .. SKIPPED > nifi-spark-receiver SKIPPED > nifi-storm-spout ... SKIPPED > nifi-example-bundle

NiFi 1.0.0 build failure in netbeans

-toolkit-tls ... SKIPPED nifi-toolkit-encrypt-config SKIPPED nifi-toolkit-assembly .. SKIPPED BUILD FAILURE

Re: BUILD FAILURE: java.lang.NoClassDefFoundError: org/apache/nifi/authorization/Authority

Matt, thanks toivo -- View this message in context: http://apache-nifi-developer-list.39713.n7.nabble.com/BUILD-FAILURE-java-lang-NoClassDefFoundError-org-apache-nifi-authorization-Authority-tp9321p9353.html Sent from the Apache NiFi Developer List mailing list archive at Nabble.com.

Re: BUILD FAILURE: java.lang.NoClassDefFoundError: org/apache/nifi/authorization/Authority

tion . SUCCESS [ > 1.065 > s] > [INFO] nifi-runtime ... SUCCESS [ > 0.226 > s] > [INFO] nifi-security .. SUCCESS [ > 1.484 > s] > [INFO]

Re: Build failure?

Upgrading to Maven 3.3.9 resolved this failure. Probably still something we'll want to either resolve for lower versions of maven (3.2.x) or list a higher minimum Maven version in the maven-enforcer-plugin. On Sun, Jan 3, 2016 at 9:55 PM, Joe Witt wrote: > And there have

Build failure?

I just updated master (since a few days ago) and now get this error -- anyone else getting it? It looks to be related to c45060f, since I checked out the version immediately before it and that one works. [INFO] Scanning for projects... [ERROR] Internal error: