Build failure

[tobin]

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 Maven is responsible for populating the assets folder?

Regards,
Tobin

build failure

[Mark Bean]

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 today.
Exact specifics unavailable, but it was Linux-based, maven 3.5.0, java
1.8.0_152. So, it must be my environment. Given the error, perhaps
something to do with available ports or port security?

Curious if anyone else has seen this error:

testRemotePortFingerprint(org.apache.nifi.fingerprint.FingerprintFactoryTest)
Time elapsed: 0.02 sec  <<< FAILURE!

org.junit.ComparisonFailure: expected: but
was:

at org.junit.Assert.assertEquals(Assert.java:115)

at org.junit.Assert.assertEquals(Assert.java:144)

at
org.apache.nifi.fingerprint.FingerprintFactoryTest.testRemotePortFingerprint(FingerprintFactoryTest.java:317)

Build failure?

[Joe Gresock]

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:
org.apache.maven.artifact.InvalidArtifactRTException: For artifact
{org.apache.nifi:nifi-riemann-processors:null:jar}: The version cannot be
empty. -> [Help 1]
org.apache.maven.InternalErrorException: Internal error:
org.apache.maven.artifact.InvalidArtifactRTException: For artifact
{org.apache.nifi:nifi-riemann-processors:null:jar}: The version cannot be
empty.
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:166)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:582)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)

This is my environment:

$ mvn -version
Apache Maven 3.2.3 (33f8c3e1027c3ddde99d3cdebad2656a31e8fdf4;
2014-08-11T16:58:10-04:00)
Maven home: c:\Program Files\apache-maven-3.2.3
Java version: 1.7.0_71, vendor: Oracle Corporation
Java home: c:\Program Files\Java\jdk1.7.0_71\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 8.1", version: "6.3", arch: "amd64", family: "windows"

-- 
I know what it is to be in need, and I know what it is to have plenty.  I
have learned the secret of being content in any and every situation,
whether well fed or hungry, whether living in plenty or in want.  I can do
all this through him who gives me strength.*-Philippians 4:12-13*

Re: Build failure

[Mike Thomsen]

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 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 Maven is responsible for populating the assets folder?
>
> Regards,
> Tobin

Maven Build Failure

[scott]

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

Re: build failure

[Aldrin Piri]

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 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 today.
> Exact specifics unavailable, but it was Linux-based, maven 3.5.0, java
> 1.8.0_152. So, it must be my environment. Given the error, perhaps
> something to do with available ports or port security?
>
> Curious if anyone else has seen this error:
>
> testRemotePortFingerprint(org.apache.nifi.fingerprint.
> FingerprintFactoryTest)
> Time elapsed: 0.02 sec  <<< FAILURE!
>
> org.junit.ComparisonFailure: expected: but
> was:
>
> at org.junit.Assert.assertEquals(Assert.java:115)
>
> at org.junit.Assert.assertEquals(Assert.java:144)
>
> at
> org.apache.nifi.fingerprint.FingerprintFactoryTest.
> testRemotePortFingerprint(FingerprintFactoryTest.java:317)
>

Re: Build failure?

[Joe Witt]

Joe

I've been building on master throughout the day today and haven't
noticed any issues.

Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
2015-11-10T11:41:47-05:00)
Maven home: /Users/jwitt/Applications/apache-maven-3.3.9
Java version: 1.8.0_66, vendor: Oracle Corporation
Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0_66.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.10.5", arch: "x86_64", family: "mac"

Thanks
Joe

On Sun, Jan 3, 2016 at 9:44 PM, Joe Gresock  wrote:
> 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:
> org.apache.maven.artifact.InvalidArtifactRTException: For artifact
> {org.apache.nifi:nifi-riemann-processors:null:jar}: The version cannot be
> empty. -> [Help 1]
> org.apache.maven.InternalErrorException: Internal error:
> org.apache.maven.artifact.InvalidArtifactRTException: For artifact
> {org.apache.nifi:nifi-riemann-processors:null:jar}: The version cannot be
> empty.
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:166)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:582)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
>
> This is my environment:
>
> $ mvn -version
> Apache Maven 3.2.3 (33f8c3e1027c3ddde99d3cdebad2656a31e8fdf4;
> 2014-08-11T16:58:10-04:00)
> Maven home: c:\Program Files\apache-maven-3.2.3
> Java version: 1.7.0_71, vendor: Oracle Corporation
> Java home: c:\Program Files\Java\jdk1.7.0_71\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 8.1", version: "6.3", arch: "amd64", family: "windows"
>
> --
> I know what it is to be in need, and I know what it is to have plenty.  I
> have learned the secret of being content in any and every situation,
> whether well fed or hungry, whether living in plenty or in want.  I can do
> all this through him who gives me strength.*-Philippians 4:12-13*

Re: Build failure?

[Joe Witt]

And there have been quite a few commits since then so I'm not quite
sure why you're seeing problems building.  However, in looking through
the bundle/poms there is room to make it more consistent so will tweak
and submit a patch for review.

On Sun, Jan 3, 2016 at 9:47 PM, Joe Witt  wrote:
> Joe
>
> I've been building on master throughout the day today and haven't
> noticed any issues.
>
> Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
> 2015-11-10T11:41:47-05:00)
> Maven home: /Users/jwitt/Applications/apache-maven-3.3.9
> Java version: 1.8.0_66, vendor: Oracle Corporation
> Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0_66.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.10.5", arch: "x86_64", family: "mac"
>
> Thanks
> Joe
>
> On Sun, Jan 3, 2016 at 9:44 PM, Joe Gresock  wrote:
>> 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:
>> org.apache.maven.artifact.InvalidArtifactRTException: For artifact
>> {org.apache.nifi:nifi-riemann-processors:null:jar}: The version cannot be
>> empty. -> [Help 1]
>> org.apache.maven.InternalErrorException: Internal error:
>> org.apache.maven.artifact.InvalidArtifactRTException: For artifact
>> {org.apache.nifi:nifi-riemann-processors:null:jar}: The version cannot be
>> empty.
>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:166)
>> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:582)
>> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
>>
>> This is my environment:
>>
>> $ mvn -version
>> Apache Maven 3.2.3 (33f8c3e1027c3ddde99d3cdebad2656a31e8fdf4;
>> 2014-08-11T16:58:10-04:00)
>> Maven home: c:\Program Files\apache-maven-3.2.3
>> Java version: 1.7.0_71, vendor: Oracle Corporation
>> Java home: c:\Program Files\Java\jdk1.7.0_71\jre
>> Default locale: en_US, platform encoding: Cp1252
>> OS name: "windows 8.1", version: "6.3", arch: "amd64", family: "windows"
>>
>> --
>> I know what it is to be in need, and I know what it is to have plenty.  I
>> have learned the secret of being content in any and every situation,
>> whether well fed or hungry, whether living in plenty or in want.  I can do
>> all this through him who gives me strength.*-Philippians 4:12-13*

Re: Build failure?

[Joe Gresock]

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 been quite a few commits since then so I'm not quite
> sure why you're seeing problems building.  However, in looking through
> the bundle/poms there is room to make it more consistent so will tweak
> and submit a patch for review.
>
> On Sun, Jan 3, 2016 at 9:47 PM, Joe Witt  wrote:
> > Joe
> >
> > I've been building on master throughout the day today and haven't
> > noticed any issues.
> >
> > Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
> > 2015-11-10T11:41:47-05:00)
> > Maven home: /Users/jwitt/Applications/apache-maven-3.3.9
> > Java version: 1.8.0_66, vendor: Oracle Corporation
> > Java home:
> /Library/Java/JavaVirtualMachines/jdk1.8.0_66.jdk/Contents/Home/jre
> > Default locale: en_US, platform encoding: UTF-8
> > OS name: "mac os x", version: "10.10.5", arch: "x86_64", family: "mac"
> >
> > Thanks
> > Joe
> >
> > On Sun, Jan 3, 2016 at 9:44 PM, Joe Gresock  wrote:
> >> 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:
> >> org.apache.maven.artifact.InvalidArtifactRTException: For artifact
> >> {org.apache.nifi:nifi-riemann-processors:null:jar}: The version cannot
> be
> >> empty. -> [Help 1]
> >> org.apache.maven.InternalErrorException: Internal error:
> >> org.apache.maven.artifact.InvalidArtifactRTException: For artifact
> >> {org.apache.nifi:nifi-riemann-processors:null:jar}: The version cannot
> be
> >> empty.
> >> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:166)
> >> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:582)
> >> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
> >> at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
> >>
> >> This is my environment:
> >>
> >> $ mvn -version
> >> Apache Maven 3.2.3 (33f8c3e1027c3ddde99d3cdebad2656a31e8fdf4;
> >> 2014-08-11T16:58:10-04:00)
> >> Maven home: c:\Program Files\apache-maven-3.2.3
> >> Java version: 1.7.0_71, vendor: Oracle Corporation
> >> Java home: c:\Program Files\Java\jdk1.7.0_71\jre
> >> Default locale: en_US, platform encoding: Cp1252
> >> OS name: "windows 8.1", version: "6.3", arch: "amd64", family: "windows"
> >>
> >> --
> >> I know what it is to be in need, and I know what it is to have plenty.
> I
> >> have learned the secret of being content in any and every situation,
> >> whether well fed or hungry, whether living in plenty or in want.  I can
> do
> >> all this through him who gives me strength.*-Philippians 4:12-13*
>



-- 
I know what it is to be in need, and I know what it is to have plenty.  I
have learned the secret of being content in any and every situation,
whether well fed or hungry, whether living in plenty or in want.  I can do
all this through him who gives me strength.*-Philippians 4:12-13*

Re: Build failure?

[Joe Witt]

Joe

Thanks for verifying that.  I just tried and replicated.  I then
applied the patch I put up last night for NIFI-1347 and it appears
resolved.

Once I get a +1 on that I'll merge to master.

Thanks
Joe

On Mon, Jan 4, 2016 at 8:41 AM, Joe Gresock  wrote:
> 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 been quite a few commits since then so I'm not quite
>> sure why you're seeing problems building.  However, in looking through
>> the bundle/poms there is room to make it more consistent so will tweak
>> and submit a patch for review.
>>
>> On Sun, Jan 3, 2016 at 9:47 PM, Joe Witt  wrote:
>> > Joe
>> >
>> > I've been building on master throughout the day today and haven't
>> > noticed any issues.
>> >
>> > Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
>> > 2015-11-10T11:41:47-05:00)
>> > Maven home: /Users/jwitt/Applications/apache-maven-3.3.9
>> > Java version: 1.8.0_66, vendor: Oracle Corporation
>> > Java home:
>> /Library/Java/JavaVirtualMachines/jdk1.8.0_66.jdk/Contents/Home/jre
>> > Default locale: en_US, platform encoding: UTF-8
>> > OS name: "mac os x", version: "10.10.5", arch: "x86_64", family: "mac"
>> >
>> > Thanks
>> > Joe
>> >
>> > On Sun, Jan 3, 2016 at 9:44 PM, Joe Gresock  wrote:
>> >> 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:
>> >> org.apache.maven.artifact.InvalidArtifactRTException: For artifact
>> >> {org.apache.nifi:nifi-riemann-processors:null:jar}: The version cannot
>> be
>> >> empty. -> [Help 1]
>> >> org.apache.maven.InternalErrorException: Internal error:
>> >> org.apache.maven.artifact.InvalidArtifactRTException: For artifact
>> >> {org.apache.nifi:nifi-riemann-processors:null:jar}: The version cannot
>> be
>> >> empty.
>> >> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:166)
>> >> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:582)
>> >> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
>> >> at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
>> >>
>> >> This is my environment:
>> >>
>> >> $ mvn -version
>> >> Apache Maven 3.2.3 (33f8c3e1027c3ddde99d3cdebad2656a31e8fdf4;
>> >> 2014-08-11T16:58:10-04:00)
>> >> Maven home: c:\Program Files\apache-maven-3.2.3
>> >> Java version: 1.7.0_71, vendor: Oracle Corporation
>> >> Java home: c:\Program Files\Java\jdk1.7.0_71\jre
>> >> Default locale: en_US, platform encoding: Cp1252
>> >> OS name: "windows 8.1", version: "6.3", arch: "amd64", family: "windows"
>> >>
>> >> --
>> >> I know what it is to be in need, and I know what it is to have plenty.
>> I
>> >> have learned the secret of being content in any and every situation,
>> >> whether well fed or hungry, whether living in plenty or in want.  I can
>> do
>> >> all this through him who gives me strength.*-Philippians 4:12-13*
>>
>
>
>
> --
> I know what it is to be in need, and I know what it is to have plenty.  I
> have learned the secret of being content in any and every situation,
> whether well fed or hungry, whether living in plenty or in want.  I can do
> all this through him who gives me strength.*-Philippians 4:12-13*

Build failure on macOS

[Mark Bean]

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 error on TestHttpClient.

[ERROR] Error occurred in starting fork, check output in log
[ERROR] Process Exit Code: 134
[ERROR] Crashed tests:
[ERROR] org.apache.nifi.remote.client.http.TestHttpClient
[ERROR] at
org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:748)
[ERROR] at
org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:305)
[ERROR] at
org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:265)
[ERROR] at
org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1314)
[ERROR] at
org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:1159)
[ERROR] at
org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:932)
[ERROR] at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
[ERROR] at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210)
[ERROR] at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156)
[ERROR] at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
[ERROR] at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
[ERROR] at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
[ERROR] at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)
[ERROR] at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
[ERROR] at
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)
[ERROR] at
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)
[ERROR] at
org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)
[ERROR] at org.apache.maven.cli.MavenCli.execute(MavenCli.java:957)
[ERROR] at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:289)
[ERROR] at org.apache.maven.cli.MavenCli.main(MavenCli.java:193)
[ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
[ERROR] at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
[ERROR] at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[ERROR] at java.lang.reflect.Method.invoke(Method.java:498)
[ERROR] at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:282)
[ERROR] at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:225)
[ERROR] at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:406)
[ERROR] at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:347)

I think I've traced this back to starting on commit
12ba579b8f6c506288458fb6cd2191ea26da2cb3. (The commit prior to that does
not have trouble building: b0b1a57b9874cbbbd57122970db96464c7dd1279)

More specifically, the breaking change introduced
io.netty:netty-all:4.1.72.Final. Previously, it was 4.0.44.Final in the
affected module, nifi-commons/nifi-site-to-site-client.)Replacing the
dependency (transitive in org.littleshoot:littleproxy) with 4.0.44.Final
allows a successful build.

So, the question is whether this is macOS [12.1] specific, or if there is
something else in my environment. I am using OpenJDK 1.8.0_312, maven
3.6.3. The build is successful on Linux (Fedora 26).

Thanks,
Mark

Re: Maven Build Failure

[Aldrin Piri]

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  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
>
>

Re: Maven Build Failure

[scott]

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-maven-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-processors: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  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

Re: Maven Build Failure

[Aldrin Piri]

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  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-processors: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  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
>>>
>>>
>>>
>

Re: Maven Build Failure

[Joe Percivall]

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 fix the error.

Joe

On Sun, Mar 25, 2018 at 10: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  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-
> processors: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  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
> >>>
> >>>
> >>>
> >
>



-- 
*Joe Percivall*
linkedin.com/in/Percivall
e: jperciv...@apache.com

Re: Maven Build Failure

[scott]

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  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-processors: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  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

Re: Maven Build Failure

[Aldrin Piri]

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  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  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  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 versi

Re: Maven Build Failure

[dattatreyabeh...@gmail.com]

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: http://apache-nifi-developer-list.39713.n7.nabble.com/

PR AppVeyor build failure

[Mark Bean]

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: Build failure on macOS

[David Handermann]

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 if it has something to do with the Netty native libraries.

Do you have any additional output in the target directory related to that
particular test class?  Unfortunately it looks like LittleProxy has not
been updated in several years, but it is useful in that test class for
verifying connectivity through a proxy server.

Regards,
David Handermann


On Mon, Jan 17, 2022 at 10:07 AM Mark Bean  wrote:

> 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 error on TestHttpClient.
>
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 134
> [ERROR] Crashed tests:
> [ERROR] org.apache.nifi.remote.client.http.TestHttpClient
> [ERROR] at
>
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:748)
> [ERROR] at
>
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:305)
> [ERROR] at
>
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:265)
> [ERROR] at
>
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1314)
> [ERROR] at
>
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:1159)
> [ERROR] at
>
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:932)
> [ERROR] at
>
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
> [ERROR] at
>
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210)
> [ERROR] at
>
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156)
> [ERROR] at
>
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
> [ERROR] at
>
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> [ERROR] at
>
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> [ERROR] at
>
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)
> [ERROR] at
>
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> [ERROR] at
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)
> [ERROR] at
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)
> [ERROR] at
> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)
> [ERROR] at org.apache.maven.cli.MavenCli.execute(MavenCli.java:957)
> [ERROR] at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:289)
> [ERROR] at org.apache.maven.cli.MavenCli.main(MavenCli.java:193)
> [ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> [ERROR] at
>
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [ERROR] at
>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [ERROR] at java.lang.reflect.Method.invoke(Method.java:498)
> [ERROR] at
>
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:282)
> [ERROR] at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:225)
> [ERROR] at
>
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:406)
> [ERROR] at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:347)
>
> I think I've traced this back to starting on commit
> 12ba579b8f6c506288458fb6cd2191ea26da2cb3. (The commit prior to that does
> not have trouble building: b0b1a57b9874cbbbd57122970db96464c7dd1279)
>
> More specifically, the breaking change introduced
> io.netty:netty-all:4.1.72.Final. Previously, it was 4.0.44.Final in the
> affected module, nifi-commons/nifi-site-to-site-client.)Replacing the
> dependency (transitive in org.littleshoot:littleproxy) with 4.0.44.Final
> allows a successful build.
>
> So, the question is whether this is macOS [12.1] specific, or if there is
> something else in my environment. I am using OpenJDK 1.8.0_312, maven
> 3.6.3. The build is successful on Linux (Fedora 26).
>
> Thanks,
> Mark
>

Re: PR AppVeyor build failure

[Joe Witt]

Mark

We've turned down the appveyor build to do little more that
compilation and it still can take a very long time.

It is not used as a gating function and we're using the
appvery/travis-ci infrastructure afforded to Apache projects so it is
likely as good as it will get for now.

What i'd say is dont worry about that and just keep rolling.

Thanks

On Wed, May 16, 2018 at 8:51 AM, Mark Bean  wrote:
> 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

NiFi 1.0.0 build failure in netbeans

[Suresh Ram]

-archetypes .. SKIPPED
nifi-processor-bundle-archetype  SKIPPED
nifi-service-bundle-archetype .. SKIPPED
nifi-external .. SKIPPED
nifi-spark-receiver  SKIPPED
nifi-storm-spout ... SKIPPED
nifi-example-bundle  SKIPPED
nifi-nifi-example-processors ... SKIPPED
nifi-example-nar ... SKIPPED
nifi-toolkit ... SKIPPED
nifi-toolkit-tls ... SKIPPED
nifi-toolkit-encrypt-config  SKIPPED
nifi-toolkit-assembly .. SKIPPED

BUILD FAILURE

Total time: 04:04 min
Finished at: 2016-10-04T17:41:21+05:30
Final Memory: 154M/852M

Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
(default-compile) on project nifi-framework-cluster: Compilation failure ->
[Help 1]

To see the full stack trace of the errors, re-run Maven with the -e switch.
Re-run Maven using the -X switch to enable full debug logging.

For more information about the errors and possible solutions, please read
the following articles:
[Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException

After correcting the problems, you can resume the build with the command
  mvn  -rf :nifi-framework-cluster

Regards,
Suresh

BUILD FAILURE for nifi-registry-web-docs

[张乐]

dear.


please help me. i get the problem in window 10 when i comiple the 
[nifi-registry-web-docs] project.thanks.



D:\zhangle29\project\nifi\nifi-registry\nifi-registry-core\nifi-registry-web-docs>mvn
 compile
[INFO] Scanning for projects...
[INFO] Inspecting build with total of 1 modules...
[INFO] Installing Nexus Staging features:
[INFO]   ... total of 1 executions of maven-deploy-plugin replaced with 
nexus-staging-maven-plugin
[INFO]
[INFO] --< org.apache.nifi.registry:nifi-registry-web-docs >---
[INFO] Building nifi-registry-web-docs 1.16.0-SNAPSHOT
[INFO] [ war ]-
[INFO]
[INFO] --- maven-enforcer-plugin:3.0.0:enforce (enforce-maven-version) @ 
nifi-registry-web-docs ---
[INFO]
[INFO] --- maven-remote-resources-plugin:1.7.0:process 
(process-resource-bundles) @ nifi-registry-web-docs ---
[INFO] Preparing remote bundle org.apache:apache-jar-resource-bundle:1.4
[INFO] Copying 3 resources from 1 bundle.
[INFO]
[INFO] --- maven-resources-plugin:2.7:resources (default-resources) @ 
nifi-registry-web-docs ---
[INFO] 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 - recompiling the module!
[INFO] Compiling 1 source file to 
D:\zhangle29\project\nifi\nifi-registry\nifi-registry-core\nifi-registry-web-docs\target\classes
[INFO] ----
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time:  3.303 s
[INFO] Finished at: 2022-01-10T10:22:35+08:00
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) 
on project nifi-registry-web-docs: Compilation failure -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException

NiFi 1.6 build failure nifi-web-ui

[luis_size]

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

[INFO] 

[INFO] Total time: 04:48 min

[INFO] Finished at: 2018-03-29T09:31:54+02:00

[INFO] Final Memory: 288M/1219M

[INFO] 

[ERROR] Failed to execute goal 
com.github.eirslett:frontend-maven-plugin:1.1:npm (npm install) on project 
nifi-web-ui: Failed to run task: 'npm --cache-min Infinity install' failed. 
(error code 1) -> [Help 1]

org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal 
com.github.eirslett:frontend-maven-plugin:1.1:npm (npm install) on project 
nifi-web-ui: Failed to run task

 at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)

 at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)

 at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)

 at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)

 at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)

 at 
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)

 at 
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)

 at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)

 at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)

 at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)

 at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)

 at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)

 at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)

 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

 at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

 at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

 at java.lang.reflect.Method.invoke(Method.java:497)

 at 
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)

 at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)

 at 
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)

 at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)

Caused by: org.apache.maven.plugin.MojoFailureException: Failed to run task

 at 
com.github.eirslett.maven.plugins.frontend.mojo.AbstractFrontendMojo.execute(AbstractFrontendMojo.java:95)

 at 
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)

 at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)

 ... 20 more

Caused by: com.github.eirslett.maven.plugins.frontend.lib.TaskRunnerException: 
'npm --cache-min Infinity install' failed. (error code 1)

 at 
com.github.eirslett.maven.plugins.frontend.lib.NodeTaskExecutor.execute(NodeTaskExecutor.java:60)

 at 
com.github.eirslett.maven.plugins.frontend.mojo.NpmMojo.execute(NpmMojo.java:62)

 at 
com.github.eirslett.maven.plugins.frontend.mojo.AbstractFrontendMojo.execute(AbstractFrontendMojo.java:89)

 ... 22 more

[ERROR] 

[ERROR] 

[ERROR] For more information about the errors and possible solutions, please 
read the following articles:

[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException

[ERROR] 

[ERROR] After correcting the problems, you can resume the build with the command

[ERROR]   mvn  -rf :nifi-web-ui

Build Failure for project nifi-toolkit-cli

[tahakashaf]

I am following this page :-  Quickstart
<https://nifi.apache.org/quickstart.html>  

*mvn -version*
Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
2015-11-10T22:11:47+05:30)
Maven home: C:\Program Files\JetBrains\IntelliJ IDEA Community Edition
2017.1.4\plugins\maven\lib\maven3
Java version: 1.8.0_131, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.8.0_131\jre
Default locale: en_US, platform encoding: Cp1252
*OS name: "windows 10", version: "10.0", arch: "amd64", family: "dos"*
Java HotSpot(TM) 64-Bit Server 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]
--------
[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 50.745 s (Wall Clock)
[INFO] Finished at: 2018-08-19T16:26:33+05:30
[INFO] Final Memory: 176M/2078M
[INFO]

[INFO] 2 KB
[INFO] --- maven-compiler-plugin:3.6.0:testCompile (groovy-tests) @
nifi-framework-nar-utils ---
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:2.20.1:test (default-test) on
project nifi-toolkit-cli: There are test failures.
[ERROR]
[ERROR] Please refer to
D:\ApacheProjects\ApacheNifi\nifi\nifi-toolkit\nifi-toolkit-cli\target\surefire-reports
for the individual test results.
[ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump,
[date].dumpstream and [date]-jvmRun[N].dumpstream.
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the
command
[ERROR]   mvn  -rf :nifi-toolkit-cli
[INFO] Changes detected - recompiling the module!
[INFO] Nothing to compile - all classes are up to date
[INFO]
[INFO] --- maven-surefire-plugin:2.20.1:test (default-test) @
nifi-framework-nar-utils ---
Destroying 1 processes
Destroying process..
Destroyed 1 processes
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m;
support was removed in 8.0



Attaching files of test results
org.apache.nifi.toolkit.cli.impl.command.TestCommandProcessor
<http://apache-nifi-developer-list.39713.n7.nabble.com/file/t1039/org.txt>  
org.apache.nifi.toolkit.cli.impl.result.TestBucketsResult
<http://apache-nifi-developer-list.39713.n7.nabble.com/file/t1039/org.txt>  
org.apache.nifi.toolkit.cli.impl.result.TestRegistryClientResult
<http://apache-nifi-developer-list.39713.n7.nabble.com/file/t1039/org.txt>  
org.apache.nifi.toolkit.cli.impl.result.TestVersionedFlowSnapshotMetadataResult
<http://apache-nifi-developer-list.39713.n7.nabble.com/file/t1039/org.txt>  
org.apache.nifi.toolkit.cli.impl.result.TestVersionedFlowsResult
<http://apache-nifi-developer-list.39713.n7.nabble.com/file/t1039/org.txt>  
org.apache.nifi.toolkit.cli.impl.result.writer.TestDynamicTableWriter
<http://apache-nifi-developer-list.39713.n7.nabble.com/file/t1039/org.txt>  
org.apache.nifi.toolkit.cli.TestCLICompleter
<http://apache-nifi-developer-list.39713.n7.nabble.com/file/t1039/org.txt>  

Please have a look over this issue.

Thanks,
Taha Naqvi




--
Sent from: http://apache-nifi-developer-list.39713.n7.nabble.com/

Re: NiFi 1.0.0 build failure in netbeans

[Andy LoPresto]

 nifi-evtx-nar .. SKIPPED
> nifi-slack-bundle .. SKIPPED
> nifi-slack-processors .. SKIPPED
> nifi-slack-nar . SKIPPED
> nifi-snmp-bundle ... SKIPPED
> nifi-snmp-processors ... SKIPPED
> nifi-snmp-nar .. SKIPPED
> nifi-datadog-bundle  SKIPPED
> nifi-datadog-reporting-task  SKIPPED
> nifi-datadog-nar ... SKIPPED
> nifi-windows-event-log-bundle .. SKIPPED
> nifi-windows-event-log-processors .. SKIPPED
> nifi-windows-event-log-nar . SKIPPED
> nifi-ignite-bundle . SKIPPED
> nifi-ignite-processors . SKIPPED
> nifi-ignite-nar  SKIPPED
> nifi-email-bundle .. SKIPPED
> nifi-email-processors .. SKIPPED
> nifi-email-nar . SKIPPED
> nifi-ranger-bundle . SKIPPED
> nifi-ranger-plugin . SKIPPED
> nifi-ranger-nar  SKIPPED
> nifi-ranger-resources .. SKIPPED
> nifi-docs .. SKIPPED
> nifi-assembly .. SKIPPED
> nifi-maven-archetypes .. SKIPPED
> nifi-processor-bundle-archetype  SKIPPED
> nifi-service-bundle-archetype ...... SKIPPED
> nifi-external .. SKIPPED
> nifi-spark-receiver  SKIPPED
> nifi-storm-spout ... SKIPPED
> nifi-example-bundle  SKIPPED
> nifi-nifi-example-processors ... SKIPPED
> nifi-example-nar ... SKIPPED
> nifi-toolkit ... SKIPPED
> nifi-toolkit-tls ... SKIPPED
> nifi-toolkit-encrypt-config  SKIPPED
> nifi-toolkit-assembly .. SKIPPED
> 
> BUILD FAILURE
> 
> Total time: 04:04 min
> Finished at: 2016-10-04T17:41:21+05:30
> Final Memory: 154M/852M
> 
> Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
> (default-compile) on project nifi-framework-cluster: Compilation failure ->
> [Help 1]
> 
> To see the full stack trace of the errors, re-run Maven with the -e switch.
> Re-run Maven using the -X switch to enable full debug logging.
> 
> For more information about the errors and possible solutions, please read
> the following articles:
> [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> 
> After correcting the problems, you can resume the build with the command
>  mvn  -rf :nifi-framework-cluster
> 
> Regards,
> Suresh



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: NiFi 1.0.0 build failure in netbeans

[sureshram]

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

Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.2:compile (default-compile)
on project nifi-framework-cluster: Compilation failure -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
(default-compile) on project nifi-framework-cluster: Compilation failure
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:862)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:286)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:197)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.apache.maven.plugin.compiler.CompilationFailureException:
Compilation failure
at
org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:913)
at
org.apache.maven.plugin.compiler.CompilerMojo.execute(CompilerMojo.java:129)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
... 20 more


For more information about the errors and possible solutions, please read
the following articles:
[Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException

~suresh




--
View this message in context: 
http://apache-nifi-developer-list.39713.n7.nabble.com/NiFi-1-0-0-build-failure-in-netbeans-tp13527p13645.html
Sent from the Apache NiFi Developer List mailing list archive at Nabble.com.

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

[Joe Witt]

Hello

The relevant details are provided further up in the build output so
please identify/share those.  They likely start with [ERROR].

Thanks

On Sun, Jan 9, 2022 at 7:47 PM 张乐  wrote:
>
> dear.
>
>
> please help me. i get the problem in window 10 when i comiple the 
> [nifi-registry-web-docs] project.thanks.
>
>
>
> D:\zhangle29\project\nifi\nifi-registry\nifi-registry-core\nifi-registry-web-docs>mvn
>  compile
> [INFO] Scanning for projects...
> [INFO] Inspecting build with total of 1 modules...
> [INFO] Installing Nexus Staging features:
> [INFO]   ... total of 1 executions of maven-deploy-plugin replaced with 
> nexus-staging-maven-plugin
> [INFO]
> [INFO] --< org.apache.nifi.registry:nifi-registry-web-docs 
> >---
> [INFO] Building nifi-registry-web-docs 1.16.0-SNAPSHOT
> [INFO] [ war 
> ]-
> [INFO]
> [INFO] --- maven-enforcer-plugin:3.0.0:enforce (enforce-maven-version) @ 
> nifi-registry-web-docs ---
> [INFO]
> [INFO] --- maven-remote-resources-plugin:1.7.0:process 
> (process-resource-bundles) @ nifi-registry-web-docs ---
> [INFO] Preparing remote bundle org.apache:apache-jar-resource-bundle:1.4
> [INFO] Copying 3 resources from 1 bundle.
> [INFO]
> [INFO] --- maven-resources-plugin:2.7:resources (default-resources) @ 
> nifi-registry-web-docs ---
> [INFO] 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 - recompiling the module!
> [INFO] Compiling 1 source file to 
> D:\zhangle29\project\nifi\nifi-registry\nifi-registry-core\nifi-registry-web-docs\target\classes
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time:  3.303 s
> [INFO] Finished at: 2022-01-10T10:22:35+08:00
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile 
> (default-compile) on project nifi-registry-web-docs: Compilation failure -> 
> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles:
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException

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

[Lars Winderling]

Have you tried as maven suggested, to run with the "-e" switch?

[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.


Best, Lars

On 1/10/22 7:11 AM, leo wrote:

Just these. That is my puzzle. I can’t get any other error info.

On 2022/01/10 03:22:25 Joe Witt wrote:

Hello

The relevant details are provided further up in the build output so
please identify/share those.  They likely start with [ERROR].

Thanks

On Sun, Jan 9, 2022 at 7:47 PM 张乐  wrote:

dear.


please help me. i get the problem in window 10 when i comiple the 
[nifi-registry-web-docs] project.thanks.



D:\zhangle29\project\nifi\nifi-registry\nifi-registry-core\nifi-registry-web-docs>mvn
 compile
[INFO] Scanning for projects...
[INFO] Inspecting build with total of 1 modules...
[INFO] Installing Nexus Staging features:
[INFO]   ... total of 1 executions of maven-deploy-plugin replaced with 
nexus-staging-maven-plugin
[INFO]
[INFO] --< org.apache.nifi.registry:nifi-registry-web-docs >---
[INFO] Building nifi-registry-web-docs 1.16.0-SNAPSHOT
[INFO] [ war ]-
[INFO]
[INFO] --- maven-enforcer-plugin:3.0.0:enforce (enforce-maven-version) @ 
nifi-registry-web-docs ---
[INFO]
[INFO] --- maven-remote-resources-plugin:1.7.0:process 
(process-resource-bundles) @ nifi-registry-web-docs ---
[INFO] Preparing remote bundle org.apache:apache-jar-resource-bundle:1.4
[INFO] Copying 3 resources from 1 bundle.
[INFO]
[INFO] --- maven-resources-plugin:2.7:resources (default-resources) @ 
nifi-registry-web-docs ---
[INFO] 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 - recompiling the module!
[INFO] Compiling 1 source file to 
D:\zhangle29\project\nifi\nifi-registry\nifi-registry-core\nifi-registry-web-docs\target\classes
[INFO] --------
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time:  3.303 s
[INFO] Finished at: 2022-01-10T10:22:35+08:00
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on 
project nifi-registry-web-docs: Compilation failure -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException

发送自 Windows 10 版邮件应用







OpenPGP_signature
Description: OpenPGP digital signature

Re: NiFi 1.6 build failure nifi-web-ui

[Sivaprasanna]

The latest master should be able to build without this error. I recently
faced this problem.  Please make sure you’re using the latest master. Take
a look at this PR :
https://github.com/apache/nifi/pull/2571

Sivaprasanna

On Thu, 29 Mar 2018 at 1:07 PM, luis_size 
wrote:

> 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
>
> [INFO]
> 
>
> [INFO] Total time: 04:48 min
>
> [INFO] Finished at: 2018-03-29T09:31:54+02:00
>
> [INFO] Final Memory: 288M/1219M
>
> [INFO]
> 
>
> [ERROR] Failed to execute goal
> com.github.eirslett:frontend-maven-plugin:1.1:npm (npm install) on project
> nifi-web-ui: Failed to run task: 'npm --cache-min Infinity install' failed.
> (error code 1) -> [Help 1]
>
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal com.github.eirslett:frontend-maven-plugin:1.1:npm (npm install) on
> project nifi-web-ui: Failed to run task
>
>  at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>
>  at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>
>  at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>
>  at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>
>  at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
>
>  at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
>
>  at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
>
>  at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
>
>  at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
>
>  at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
>
>  at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
>
>  at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
>
>  at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
>
>  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>
>  at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>
>  at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>
>  at java.lang.reflect.Method.invoke(Method.java:497)
>
>  at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
>
>  at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
>
>  at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
>
>  at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
>
> Caused by: org.apache.maven.plugin.MojoFailureException: Failed to run task
>
>  at
> com.github.eirslett.maven.plugins.frontend.mojo.AbstractFrontendMojo.execute(AbstractFrontendMojo.java:95)
>
>  at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>
>  at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
>
>  ... 20 more
>
> Caused by:
> com.github.eirslett.maven.plugins.frontend.lib.TaskRunnerException: 'npm
> --cache-min Infinity install' failed. (error code 1)
>
>  at
> com.github.eirslett.maven.plugins.frontend.lib.NodeTaskExecutor.execute(NodeTaskExecutor.java:60)
>
>  at
> com.github.eirslett.maven.plugins.frontend.mojo.NpmMojo.execute(NpmMojo.java:62)
>
>  at
> com.github.eirslett.maven.plugins.frontend.mojo.AbstractFrontendMojo.execute(AbstractFrontendMojo.java:89)
>
>  ... 22 more
>
> [ERROR]
>
> [ERROR]
>
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
>
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
>
> [ERROR]
>
> [ERROR] After correcting the problems, you can resume the build with the
> command
>
> [ERROR]   mvn  -rf :nifi-web-ui
>
>

Re: Build Failure for project nifi-toolkit-cli

[Bryan Bende]

Looks like all of the links go to the same test failure for
TestCLICompleter, which seems to be failing because it can't find a
file in src/test/resources [1].

The part of the CLI that is doing to file completion is from the JLine
library, so we don't really have control over making that work on
Windows.

Maybe we can add something to the unit test so that it doesn't run
when building on Windows.

I'm also not sure if this is just a build issue, or if the file
auto-completion would actually not work on Windows when using the
built CLI.

[1] 
https://github.com/apache/nifi/blob/master/nifi-toolkit/nifi-toolkit-cli/src/test/java/org/apache/nifi/toolkit/cli/TestCLICompleter.java#L213-L221

On Sun, Aug 19, 2018 at 7:00 AM, tahakashaf  wrote:
> I am following this page :-  Quickstart
> <https://nifi.apache.org/quickstart.html>
>
> *mvn -version*
> Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
> 2015-11-10T22:11:47+05:30)
> Maven home: C:\Program Files\JetBrains\IntelliJ IDEA Community Edition
> 2017.1.4\plugins\maven\lib\maven3
> Java version: 1.8.0_131, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.8.0_131\jre
> Default locale: en_US, platform encoding: Cp1252
> *OS name: "windows 10", version: "10.0", arch: "amd64", family: "dos"*
> Java HotSpot(TM) 64-Bit Server 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]
> 
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time: 50.745 s (Wall Clock)
> [INFO] Finished at: 2018-08-19T16:26:33+05:30
> [INFO] Final Memory: 176M/2078M
> [INFO]
> 
> [INFO] 2 KB
> [INFO] --- maven-compiler-plugin:3.6.0:testCompile (groovy-tests) @
> nifi-framework-nar-utils ---
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.20.1:test (default-test) on
> project nifi-toolkit-cli: There are test failures.
> [ERROR]
> [ERROR] Please refer to
> D:\ApacheProjects\ApacheNifi\nifi\nifi-toolkit\nifi-toolkit-cli\target\surefire-reports
> for the individual test results.
> [ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump,
> [date].dumpstream and [date]-jvmRun[N].dumpstream.
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR]   mvn  -rf :nifi-toolkit-cli
> [INFO] Changes detected - recompiling the module!
> [INFO] Nothing to compile - all classes are up to date
> [INFO]
> [INFO] --- maven-surefire-plugin:2.20.1:test (default-test) @
> nifi-framework-nar-utils ---
> Destroying 1 processes
> Destroying process..
> Destroyed 1 processes
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m;
> support was removed in 8.0
>
>
>
> Attaching files of test results
> org.apache.nifi.toolkit.cli.impl.command.TestCommandProcessor
> <http://apache-nifi-developer-list.39713.n7.nabble.com/file/t1039/org.txt>
> org.apache.nifi.toolkit.cli.impl.result.TestBucketsResult
> <http://apache-nifi-developer-list.39713.n7.nabble.com/file/t1039/org.txt>
> org.apache.nifi.toolkit.cli.impl.result.TestRegistryClientResult
> <http://apache-nifi-developer-list.39713.n7.nabble.com/file/t1039/org.txt>
> org.apache.nifi.toolkit.cli.impl.result.TestVersionedFlowSnapshotMetadataResult
> <http://apache-nifi-developer-list.39713.n7.nabble.com/file/t1039/org.txt>
> org.apache.nifi.toolkit.cli.impl.result.TestVersionedFlowsResult
> <http://apache-nifi-developer-list.39713.n7.nabble.com/file/t1039/org.txt>
> org.apache.nifi.toolkit.cli.impl.result.writer.TestDynamicTableWriter
> <http://apache-nifi-developer-list.39713.n7.nabble.com/file/t1039/org.txt>
> org.apache.nifi.toolkit.cli.TestCLICompleter
> <http://apache-nifi-developer-list.39713.n7.nabble.com/file/t1039/org.txt>
>
> Please have a look over this issue.
>
> Thanks,
> Taha Naqvi
>
>
>
>
> --
> Sent from: http://apache-nifi-developer-list.39713.n7.nabble.com/

Re: Build Failure for project nifi-toolkit-cli

[tahakashaf]

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 resolve by  changing this 
   * private static final String TEST_RES_PATH =
NiFiGroovyTest.getClassLoader().getResource(".").toURI().getPath()*
  --TO
*private static final String TEST_RES_PATH =
Paths.get(NiFiGroovyTest.getClassLoader().getResource(".").toURI()).toString()*

But again in the process of build I face this:-
*TestFileSystemRepo unit test failures*

http://mail-archives.apache.org/mod_mbox/nifi-issues/201710.mbox/%3cjira.13106295.150687503.247104.1506875040...@atlassian.jira%3E



--
Sent from: http://apache-nifi-developer-list.39713.n7.nabble.com/

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

[Toivo Adams]

I have a weird problem.
NiFi build fails in Eclipse.
branch 'master'

[INFO]

[INFO] Reactor Summary:
[INFO] 
[INFO] nifi ... SUCCESS [  2.801
s]
[INFO] nifi-api ... SUCCESS [  2.003
s]
[INFO] nifi-commons ... SUCCESS [  0.056
s]
[INFO] nifi-security-utils  SUCCESS [  0.153
s]
[INFO] nifi-utils . SUCCESS [  5.745
s]
[INFO] nifi-data-provenance-utils . SUCCESS [  0.192
s]
[INFO] nifi-flowfile-packager . SUCCESS [  0.363
s]
[INFO] nifi-expression-language ... SUCCESS [  5.391
s]
[INFO] nifi-logging-utils . SUCCESS [  0.064
s]
[INFO] nifi-properties  SUCCESS [  0.356
s]
[INFO] nifi-socket-utils .. SUCCESS [  0.351
s]
[INFO] nifi-web-utils . SUCCESS [  0.294
s]
[INFO] nifi-processor-utils ... SUCCESS [  0.568
s]
[INFO] nifi-write-ahead-log ... SUCCESS [  5.435
s]
[INFO] nifi-nar-bundles ... SUCCESS [  0.038
s]
[INFO] nifi-framework-bundle .. SUCCESS [  0.110
s]
[INFO] nifi-framework . SUCCESS [  0.052
s]
[INFO] nifi-client-dto  SUCCESS [  0.238
s]
[INFO] nifi-site-to-site-client ... SUCCESS [  0.823
s]
[INFO] nifi-hl7-query-language  SUCCESS [  1.252
s]
[INFO] nifi-hadoop-utils .. SUCCESS [  1.929
s]
[INFO] nifi-bootstrap . SUCCESS [  0.231
s]
[INFO] nifi-mock .. SUCCESS [  0.597
s]
[INFO] nifi-nar-utils . SUCCESS [  0.449
s]
[INFO] nifi-framework-core-api  SUCCESS [  0.310
s]
[INFO] nifi-documentation . SUCCESS [  1.065
s]
[INFO] nifi-runtime ... SUCCESS [  0.226
s]
[INFO] nifi-security .. SUCCESS [  1.484
s]
[INFO] nifi-user-actions .. SUCCESS [  0.103
s]
[INFO] nifi-administration  FAILURE [  0.672
s]
. . .

[INFO]
----
[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 36.924 s
[INFO] Finished at: 2016-04-19T16:32:02+03:00
[INFO] Final Memory: 99M/397M
[INFO]

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:2.18:test (default-test) on
project nifi-administration: Execution default-test of goal
org.apache.maven.plugins:maven-surefire-plugin:2.18:test failed: There was
an error in the forked process
[ERROR] java.lang.NoClassDefFoundError:
org/apache/nifi/authorization/Authority
[ERROR] at java.lang.Class.getDeclaredMethods0(Native Method)
[ERROR] at java.lang.Class.privateGetDeclaredMethods(Class.java:2701)
[ERROR] at java.lang.Class.privateGetMethodRecursive(Class.java:3048)
[ERROR] at java.lang.Class.getMethod0(Class.java:3018)
[ERROR] at java.lang.Class.getMethod(Class.java:1784)
[ERROR] at
org.apache.maven.surefire.util.ReflectionUtils.tryGetMethod(ReflectionUtils.java:57)
[ERROR] at
org.apache.maven.surefire.common.junit3.JUnit3TestChecker.isSuiteOnly(JUnit3TestChecker.java:64)
[ERROR] at
org.apache.maven.surefire.common.junit3.JUnit3TestChecker.isValidJUnit3Test(JUnit3TestChecker.java:59)
[ERROR] at
org.apache.maven.surefire.common.junit3.JUnit3TestChecker.accept(JUnit3TestChecker.java:54)
[ERROR] at
org.apache.maven.surefire.common.junit4.JUnit4TestChecker.accept(JUnit4TestChecker.java:52)
[ERROR] at
org.apache.maven.surefire.util.DefaultScanResult.applyFilter(DefaultScanResult.java:97)
[ERROR] at
org.apache.maven.surefire.junit4.JUnit4Provider.scanClassPath(JUnit4Provider.java:222)
[ERROR] at
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:107)
[ERROR] at
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203)
[ERROR] at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155)
[ERROR] at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
[ERROR] Caused by: java.lang.ClassNotFoundException:
org.apache.nifi.authorization.Authority
[ERROR] at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
[ERROR] at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
[ERROR] at sun.mis

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

[leo]

Just these. That is my puzzle. I can’t get any other error info.

On 2022/01/10 03:22:25 Joe Witt wrote:
> Hello
> 
> The relevant details are provided further up in the build output so
> please identify/share those.  They likely start with [ERROR].
> 
> Thanks
> 
> On Sun, Jan 9, 2022 at 7:47 PM 张乐  wrote:
> >
> > dear.
> >
> >
> > please help me. i get the problem in window 10 when i comiple the 
> > [nifi-registry-web-docs] project.thanks.
> >
> >
> >
> > D:\zhangle29\project\nifi\nifi-registry\nifi-registry-core\nifi-registry-web-docs>mvn
> >  compile
> > [INFO] Scanning for projects...
> > [INFO] Inspecting build with total of 1 modules...
> > [INFO] Installing Nexus Staging features:
> > [INFO]   ... total of 1 executions of maven-deploy-plugin replaced with 
> > nexus-staging-maven-plugin
> > [INFO]
> > [INFO] --< org.apache.nifi.registry:nifi-registry-web-docs 
> > >---
> > [INFO] Building nifi-registry-web-docs 1.16.0-SNAPSHOT
> > [INFO] [ war 
> > ]-
> > [INFO]
> > [INFO] --- maven-enforcer-plugin:3.0.0:enforce (enforce-maven-version) @ 
> > nifi-registry-web-docs ---
> > [INFO]
> > [INFO] --- maven-remote-resources-plugin:1.7.0:process 
> > (process-resource-bundles) @ nifi-registry-web-docs ---
> > [INFO] Preparing remote bundle org.apache:apache-jar-resource-bundle:1.4
> > [INFO] Copying 3 resources from 1 bundle.
> > [INFO]
> > [INFO] --- maven-resources-plugin:2.7:resources (default-resources) @ 
> > nifi-registry-web-docs ---
> > [INFO] 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 - recompiling the module!
> > [INFO] Compiling 1 source file to 
> > D:\zhangle29\project\nifi\nifi-registry\nifi-registry-core\nifi-registry-web-docs\target\classes
> > [INFO] 
> > 
> > [INFO] BUILD FAILURE
> > [INFO] 
> > 
> > [INFO] Total time:  3.303 s
> > [INFO] Finished at: 2022-01-10T10:22:35+08:00
> > [INFO] 
> > 
> > [ERROR] Failed to execute goal 
> > org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile 
> > (default-compile) on project nifi-registry-web-docs: Compilation failure -> 
> > [Help 1]
> > [ERROR]
> > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> > switch.
> > [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> > [ERROR]
> > [ERROR] For more information about the errors and possible solutions, 
> > please read the following articles:
> > [ERROR] [Help 1] 
> > http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> 
发送自 Windows 10 版邮件应用

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

[Joe Gresock]

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-codemirror/-/angular-ui-codemirror-0.3.0.tgz
[ERROR] npm ERR! fetch failed
https://registry.npmjs.org/angular-ui-codemirror/-/angular-ui-codemirror-0.3.0.tgz
[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-codemirror/-/angular-ui-codemirror-0.3.0.tgz
[ERROR] npm ERR! fetch failed
https://registry.npmjs.org/angular-ui-codemirror/-/angular-ui-codemirror-0.3.0.tgz

[ERROR] Failed to execute goal
com.github.eirslett:frontend-maven-plugin:1.0:npm (npm install) on project
nifi-jolt-transform-json-ui: Failed to run task: 'npm --cache-min Infinity
install' failed. (error code 1) -> [Help 1]


-- 
I know what it is to be in need, and I know what it is to have plenty.  I
have learned the secret of being content in any and every situation,
whether well fed or hungry, whether living in plenty or in want.  I can do
all this through him who gives me strength.*-Philippians 4:12-13*

Build failure on Mac OS X with DS_STORE files

[Otto Fowler]

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 the DS_STORE is detected and has an url built and returned for it.

The test does not pass in a FileNamesFilter, which could be used to filter
these files out I suppose.

I am wondering if anyone is building successfully on Mac OS X?

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

[Matt Gilman]

Toivo,

That class was removed on master with NIFI-1551 as we move toward the new
Authorizer API [1]. Can you verify that you have everything up to date and
you've cleaned your code base locally.

# dry run
git clean -dn

# actually do it
git clean -df

Please be careful with that command as it will also attempt to delete any
unstaged changes. Always a good idea to do the dry run first to make sure
it's not going to delete anything you're currently working on.

Once your up to date and there are no extraneous files try building again.
Thanks.

Matt

[1] https://issues.apache.org/jira/browse/NIFI-1550

On Tue, Apr 19, 2016 at 8:48 AM, Toivo Adams  wrote:

> I have a weird problem.
> NiFi build fails in Eclipse.
> branch 'master'
>
> [INFO]
> 
> [INFO] Reactor Summary:
> [INFO]
> [INFO] nifi ... SUCCESS [
> 2.801
> s]
> [INFO] nifi-api ... SUCCESS [
> 2.003
> s]
> [INFO] nifi-commons ... SUCCESS [
> 0.056
> s]
> [INFO] nifi-security-utils  SUCCESS [
> 0.153
> s]
> [INFO] nifi-utils . SUCCESS [
> 5.745
> s]
> [INFO] nifi-data-provenance-utils . SUCCESS [
> 0.192
> s]
> [INFO] nifi-flowfile-packager . SUCCESS [
> 0.363
> s]
> [INFO] nifi-expression-language ... SUCCESS [
> 5.391
> s]
> [INFO] nifi-logging-utils . SUCCESS [
> 0.064
> s]
> [INFO] nifi-properties  SUCCESS [
> 0.356
> s]
> [INFO] nifi-socket-utils .. SUCCESS [
> 0.351
> s]
> [INFO] nifi-web-utils . SUCCESS [
> 0.294
> s]
> [INFO] nifi-processor-utils ... SUCCESS [
> 0.568
> s]
> [INFO] nifi-write-ahead-log ... SUCCESS [
> 5.435
> s]
> [INFO] nifi-nar-bundles ... SUCCESS [
> 0.038
> s]
> [INFO] nifi-framework-bundle .. SUCCESS [
> 0.110
> s]
> [INFO] nifi-framework . SUCCESS [
> 0.052
> s]
> [INFO] nifi-client-dto  SUCCESS [
> 0.238
> s]
> [INFO] nifi-site-to-site-client ... SUCCESS [
> 0.823
> s]
> [INFO] nifi-hl7-query-language  SUCCESS [
> 1.252
> s]
> [INFO] nifi-hadoop-utils .. SUCCESS [
> 1.929
> s]
> [INFO] nifi-bootstrap . SUCCESS [
> 0.231
> s]
> [INFO] nifi-mock .. SUCCESS [
> 0.597
> s]
> [INFO] nifi-nar-utils . SUCCESS [
> 0.449
> s]
> [INFO] nifi-framework-core-api  SUCCESS [
> 0.310
> s]
> [INFO] nifi-documentation . SUCCESS [
> 1.065
> s]
> [INFO] nifi-runtime ... SUCCESS [
> 0.226
> s]
> [INFO] nifi-security .. SUCCESS [
> 1.484
> s]
> [INFO] nifi-user-actions .. SUCCESS [
> 0.103
> s]
> [INFO] nifi-administration  FAILURE [
> 0.672
> s]
> . . .
>
> [INFO]
> 
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time: 36.924 s
> [INFO] Finished at: 2016-04-19T16:32:02+03:00
> [INFO] Final Memory: 99M/397M
> [INFO]
> 
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.18:test (default-test) on
> project nifi-administration: Execution default-test of goal
> org.apache.maven.plugins:maven-surefire-plugin:2.18:test failed: There was
> an error in the forked process
> [ERROR] java.lang.NoClassDefFoundError:
> org/apache/nifi/authorization/Authority
> [ERROR] at java.lang.Class.getDeclaredMethods0(Native Method)
> [ERROR] at java.lang.Class.privateGetDeclaredMethods(Class.java:2701)
> [ERROR] at java.lang.Class.privateGetMethodRecursive(Class.java:3048)
> [ERROR] at java.lang.Class.getMethod0(Class.java:3018)
> [ERROR] at java.lang.Class.getMethod(Class.java:1784)
> [ERROR] at
>
> org.apache.maven.surefire.util.ReflectionUtils.tryGetMethod(ReflectionUtils.java:57)

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

[Toivo Adams]

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: Master build failure with nifi-jolt-transform-json-ui?

[Bryan Rosander]

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  wrote:

> 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-codemirror/-/
> angular-ui-codemirror-0.3.0.tgz
> [ERROR] npm ERR! fetch failed
> https://registry.npmjs.org/angular-ui-codemirror/-/
> angular-ui-codemirror-0.3.0.tgz
> [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-codemirror/-/
> angular-ui-codemirror-0.3.0.tgz
> [ERROR] npm ERR! fetch failed
> https://registry.npmjs.org/angular-ui-codemirror/-/
> angular-ui-codemirror-0.3.0.tgz
>
> [ERROR] Failed to execute goal
> com.github.eirslett:frontend-maven-plugin:1.0:npm (npm install) on project
> nifi-jolt-transform-json-ui: Failed to run task: 'npm --cache-min Infinity
> install' failed. (error code 1) -> [Help 1]
>
>
> --
> I know what it is to be in need, and I know what it is to have plenty.  I
> have learned the secret of being content in any and every situation,
> whether well fed or hungry, whether living in plenty or in want.  I can do
> all this through him who gives me strength.*-Philippians 4:12-13*
>

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

[Joe Percivall]

This is likely a side-affect of the DDOS attack on DNS servers on the east 
coast.

http://gizmodo.com/this-is-probably-why-half-the-internet-shut-down-today-1788062835

 
Joe

- - - - - - 
Joseph Percivall
linkedin.com/in/Percivall
e: joeperciv...@yahoo.com



On Friday, October 21, 2016 10:04 AM, Bryan Rosander  
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  wrote:

> 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-codemirror/-/
> angular-ui-codemirror-0.3.0.tgz
> [ERROR] npm ERR! fetch failed
> https://registry.npmjs.org/angular-ui-codemirror/-/
> angular-ui-codemirror-0.3.0.tgz
> [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-codemirror/-/
> angular-ui-codemirror-0.3.0.tgz
> [ERROR] npm ERR! fetch failed
> https://registry.npmjs.org/angular-ui-codemirror/-/
> angular-ui-codemirror-0.3.0.tgz
>
> [ERROR] Failed to execute goal
> com.github.eirslett:frontend-maven-plugin:1.0:npm (npm install) on project
> nifi-jolt-transform-json-ui: Failed to run task: 'npm --cache-min Infinity
> install' failed. (error code 1) -> [Help 1]
>
>
> --
> I know what it is to be in need, and I know what it is to have plenty.  I
> have learned the secret of being content in any and every situation,
> whether well fed or hungry, whether living in plenty or in want.  I can do
> all this through him who gives me strength.*-Philippians 4:12-13*
>

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

[Bryan Rosander]

That link from first email works for me now, maybe worth trying again?

On Fri, Oct 21, 2016 at 10:15 AM, Joe Percivall <
joeperciv...@yahoo.com.invalid> wrote:

> This is likely a side-affect of the DDOS attack on DNS servers on the east
> coast.
>
> http://gizmodo.com/this-is-probably-why-half-the-internet-shut-down-today-
> 1788062835
>
>
> Joe
>
> - - - - - -
> Joseph Percivall
> linkedin.com/in/Percivall
> e: joeperciv...@yahoo.com
>
>
>
> On Friday, October 21, 2016 10:04 AM, Bryan Rosander <
> bryanrosan...@gmail.com> 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  wrote:
>
> > 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-codemirror/-/
> > angular-ui-codemirror-0.3.0.tgz
> > [ERROR] npm ERR! fetch failed
> > https://registry.npmjs.org/angular-ui-codemirror/-/
> > angular-ui-codemirror-0.3.0.tgz
> > [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-codemirror/-/
> > angular-ui-codemirror-0.3.0.tgz
> > [ERROR] npm ERR! fetch failed
> > https://registry.npmjs.org/angular-ui-codemirror/-/
> > angular-ui-codemirror-0.3.0.tgz
> >
> > [ERROR] Failed to execute goal
> > com.github.eirslett:frontend-maven-plugin:1.0:npm (npm install) on
> project
> > nifi-jolt-transform-json-ui: Failed to run task: 'npm --cache-min
> Infinity
> > install' failed. (error code 1) -> [Help 1]
> >
> >
> > --
> > I know what it is to be in need, and I know what it is to have plenty.  I
> > have learned the secret of being content in any and every situation,
> > whether well fed or hungry, whether living in plenty or in want.  I can
> do
> > all this through him who gives me strength.*-Philippians 4:12-13*
> >
>

Re: Build failure on Mac OS X with DS_STORE files

[Otto Fowler]

@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);
assertEquals(2, urls.length);
}


resolves the issue, and I am able to build everything.


On February 8, 2017 at 22:39:53, Otto Fowler (ottobackwa...@gmail.com)
wrote:

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 the DS_STORE is detected and has an url built and returned for it.

The test does not pass in a FileNamesFilter, which could be used to filter
these files out I suppose.

I am wondering if anyone is building successfully on Mac OS X?

Re: Build failure on Mac OS X with DS_STORE files

[Otto Fowler]

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 = "src/test/resources/TestClassLoaderUtils";
URL[] urls = ClassLoaderUtils.getURLsForClasspath(jarFilePath,
(dir,name)->name.compareTo(".DS_Store") == 0, false);
assertEquals(2, urls.length);
}


resolves the issue, and I am able to build everything.


On February 8, 2017 at 22:39:53, Otto Fowler (ottobackwa...@gmail.com)
wrote:

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 the DS_STORE is detected and has an url built and returned for it.

The test does not pass in a FileNamesFilter, which could be used to filter
these files out I suppose.

I am wondering if anyone is building successfully on Mac OS X?

Re: Build failure on Mac OS X with DS_STORE files

[Koji Kawamura]

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 workaround and I think we should resolve the issue.
By looking at the usage of that method, such as DBCPConnectionPool, or
JoltTransformJSON, those uses file name filter like this:

(dir, name) -> name != null && name.endsWith(".jar")

While filtering out specific .DS_Store works, targeting only name
ending with .jar looks more generic work around.

Would you mind open a JIRA and send a PR? I'd happy to review!

Thanks,
Koji

On Thu, Feb 9, 2017 at 1:20 PM, Otto Fowler  wrote:
> 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 = "src/test/resources/TestClassLoaderUtils";
> URL[] urls = ClassLoaderUtils.getURLsForClasspath(jarFilePath,
> (dir,name)->name.compareTo(".DS_Store") == 0, false);
> assertEquals(2, urls.length);
> }
>
>
> resolves the issue, and I am able to build everything.
>
>
> On February 8, 2017 at 22:39:53, Otto Fowler (ottobackwa...@gmail.com)
> wrote:
>
> 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 the DS_STORE is detected and has an url built and returned for it.
>
> The test does not pass in a FileNamesFilter, which could be used to filter
> these files out I suppose.
>
> I am wondering if anyone is building successfully on Mac OS X?

Re: Build failure on Mac OS X with DS_STORE files

[Koji Kawamura]

Excuse me, I forgot to add a link that I referred on how to create
.DS_Store file.
https://discussions.apple.com/thread/5064875?start=0&tstart=0

On Thu, Feb 9, 2017 at 11:02 PM, Koji Kawamura  wrote:
> 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 workaround and I think we should resolve the issue.
> By looking at the usage of that method, such as DBCPConnectionPool, or
> JoltTransformJSON, those uses file name filter like this:
>
> (dir, name) -> name != null && name.endsWith(".jar")
>
> While filtering out specific .DS_Store works, targeting only name
> ending with .jar looks more generic work around.
>
> Would you mind open a JIRA and send a PR? I'd happy to review!
>
> Thanks,
> Koji
>
> On Thu, Feb 9, 2017 at 1:20 PM, Otto Fowler  wrote:
>> 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 = "src/test/resources/TestClassLoaderUtils";
>> URL[] urls = ClassLoaderUtils.getURLsForClasspath(jarFilePath,
>> (dir,name)->name.compareTo(".DS_Store") == 0, false);
>> assertEquals(2, urls.length);
>> }
>>
>>
>> resolves the issue, and I am able to build everything.
>>
>>
>> On February 8, 2017 at 22:39:53, Otto Fowler (ottobackwa...@gmail.com)
>> wrote:
>>
>> 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 the DS_STORE is detected and has an url built and returned for it.
>>
>> The test does not pass in a FileNamesFilter, which could be used to filter
>> these files out I suppose.
>>
>> I am wondering if anyone is building successfully on Mac OS X?

Re: Build failure on Mac OS X with DS_STORE files

[Otto Fowler]

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 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 workaround and I think we should resolve the issue.
By looking at the usage of that method, such as DBCPConnectionPool, or
JoltTransformJSON, those uses file name filter like this:

(dir, name) -> name != null && name.endsWith(".jar")

While filtering out specific .DS_Store works, targeting only name
ending with .jar looks more generic work around.

Would you mind open a JIRA and send a PR? I'd happy to review!

Thanks,
Koji

On Thu, Feb 9, 2017 at 1:20 PM, Otto Fowler 
wrote:
> 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 = "src/test/resources/TestClassLoaderUtils";
> URL[] urls = ClassLoaderUtils.getURLsForClasspath(jarFilePath,
> (dir,name)->name.compareTo(".DS_Store") == 0, false);
> assertEquals(2, urls.length);
> }
>
>
> resolves the issue, and I am able to build everything.
>
>
> On February 8, 2017 at 22:39:53, Otto Fowler (ottobackwa...@gmail.com)
> wrote:
>
> 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 the DS_STORE is detected and has an url built and returned for
it.
>
> The test does not pass in a FileNamesFilter, which could be used to
filter
> these files out I suppose.
>
> I am wondering if anyone is building successfully on Mac OS X?

Re: Build failure on Mac OS X with DS_STORE files

[Koji Kawamura]

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)
> wrote:
>
> 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 workaround and I think we should resolve the issue.
> By looking at the usage of that method, such as DBCPConnectionPool, or
> JoltTransformJSON, those uses file name filter like this:
>
> (dir, name) -> name != null && name.endsWith(".jar")
>
> While filtering out specific .DS_Store works, targeting only name
> ending with .jar looks more generic work around.
>
> Would you mind open a JIRA and send a PR? I'd happy to review!
>
> Thanks,
> Koji
>
> On Thu, Feb 9, 2017 at 1:20 PM, Otto Fowler  wrote:
>> 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 = "src/test/resources/TestClassLoaderUtils";
>> URL[] urls = ClassLoaderUtils.getURLsForClasspath(jarFilePath,
>> (dir,name)->name.compareTo(".DS_Store") == 0, false);
>> assertEquals(2, urls.length);
>> }
>>
>>
>> resolves the issue, and I am able to build everything.
>>
>>
>> On February 8, 2017 at 22:39:53, Otto Fowler (ottobackwa...@gmail.com)
>> wrote:
>>
>> 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 the DS_STORE is detected and has an url built and returned for it.
>>
>> The test does not pass in a FileNamesFilter, which could be used to filter
>> these files out I suppose.
>>
>> I am wondering if anyone is building successfully on Mac OS X?

Re: Build failure on Mac OS X with DS_STORE files

[Otto Fowler]

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 to ask, does anyone working on NiFi use a mac?   The next problems I
have are not with .DS_Store files or anything ‘mac centric’, they are with
Nashorn Java script types in the ScriptingProcessor tests…..

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 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 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 workaround and I think we should resolve the issue.
> By looking at the usage of that method, such as DBCPConnectionPool, or
> JoltTransformJSON, those uses file name filter like this:
>
> (dir, name) -> name != null && name.endsWith(".jar")
>
> While filtering out specific .DS_Store works, targeting only name
> ending with .jar looks more generic work around.
>
> Would you mind open a JIRA and send a PR? I'd happy to review!
>
> Thanks,
> Koji
>
> On Thu, Feb 9, 2017 at 1:20 PM, Otto Fowler 
wrote:
>> 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 = "src/test/resources/TestClassLoaderUtils";
>> URL[] urls = ClassLoaderUtils.getURLsForClasspath(jarFilePath,
>> (dir,name)->name.compareTo(".DS_Store") == 0, false);
>> assertEquals(2, urls.length);
>> }
>>
>>
>> resolves the issue, and I am able to build everything.
>>
>>
>> On February 8, 2017 at 22:39:53, Otto Fowler (ottobackwa...@gmail.com)
>> wrote:
>>
>> 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 the DS_STORE is detected and has an url built and returned for
it.
>>
>> The test does not pass in a FileNamesFilter, which could be used to
filter
>> these files out I suppose.
>>
>> I am wondering if anyone is building successfully on Mac OS X?

Re: Build failure on Mac OS X with DS_STORE files

[Joe Skora]

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 since I built on the Mac, I can check it tonight.

Regards,
Joe

On Thu, Feb 9, 2017 at 10:59 AM, Otto Fowler 
wrote:

> 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 to ask, does anyone working on NiFi use a mac?   The next problems I
> have are not with .DS_Store files or anything ‘mac centric’, they are with
> Nashorn Java script types in the ScriptingProcessor tests…..
>
> 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 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 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 workaround and I think we should resolve the issue.
> > By looking at the usage of that method, such as DBCPConnectionPool, or
> > JoltTransformJSON, those uses file name filter like this:
> >
> > (dir, name) -> name != null && name.endsWith(".jar")
> >
> > While filtering out specific .DS_Store works, targeting only name
> > ending with .jar looks more generic work around.
> >
> > Would you mind open a JIRA and send a PR? I'd happy to review!
> >
> > Thanks,
> > Koji
> >
> > On Thu, Feb 9, 2017 at 1:20 PM, Otto Fowler 
> wrote:
> >> 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 = "src/test/resources/TestClassLoaderUtils";
> >> URL[] urls = ClassLoaderUtils.getURLsForClasspath(jarFilePath,
> >> (dir,name)->name.compareTo(".DS_Store") == 0, false);
> >> assertEquals(2, urls.length);
> >> }
> >>
> >>
> >> resolves the issue, and I am able to build everything.
> >>
> >>
> >> On February 8, 2017 at 22:39:53, Otto Fowler (ottobackwa...@gmail.com)
> >> wrote:
> >>
> >> 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 the DS_STORE is detected and has an url built and returned for
> it.
> >>
> >> The test does not pass in a FileNamesFilter, which could be used to
> filter
> >> these files out I suppose.
> >>
> >> I am wondering if anyone is building successfully on Mac OS X?
>

Re: Build failure on Mac OS X with DS_STORE files

[Otto Fowler]

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 patch *would* be?


On February 9, 2017 at 11:11:55, Joe Skora (jsk...@gmail.com) wrote:

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 since I built on the Mac, I can check it tonight.

Regards,
Joe

On Thu, Feb 9, 2017 at 10:59 AM, Otto Fowler 
wrote:

> 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 to ask, does anyone working on NiFi use a mac? The next problems I
> have are not with .DS_Store files or anything ‘mac centric’, they are
with
> Nashorn Java script types in the ScriptingProcessor tests…..
>
> 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 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 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 workaround and I think we should resolve the issue.
> > By looking at the usage of that method, such as DBCPConnectionPool, or
> > JoltTransformJSON, those uses file name filter like this:
> >
> > (dir, name) -> name != null && name.endsWith(".jar")
> >
> > While filtering out specific .DS_Store works, targeting only name
> > ending with .jar looks more generic work around.
> >
> > Would you mind open a JIRA and send a PR? I'd happy to review!
> >
> > Thanks,
> > Koji
> >
> > On Thu, Feb 9, 2017 at 1:20 PM, Otto Fowler 
> wrote:
> >> 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 = "src/test/resources/TestClassLoaderUtils";
> >> URL[] urls = ClassLoaderUtils.getURLsForClasspath(jarFilePath,
> >> (dir,name)->name.compareTo(".DS_Store") == 0, false);
> >> assertEquals(2, urls.length);
> >> }
> >>
> >>
> >> resolves the issue, and I am able to build everything.
> >>
> >>
> >> On February 8, 2017 at 22:39:53, Otto Fowler (ottobackwa...@gmail.com)
> >> wrote:
> >>
> >> 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 the DS_STORE is detected and has an url built and returned for
> it.
> >>
> >> The test does not pass in a FileNamesFilter, which could be used to
> filter
> >> these files out I suppose.
> >>
> >> I am wondering if anyone is building successfully on Mac OS X?
>

Re: Build failure on Mac OS X with DS_STORE files

[Koji Kawamura]

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 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 patch *would* be?
>
>
> On February 9, 2017 at 11:11:55, Joe Skora (jsk...@gmail.com) wrote:
>
> 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 since I built on the Mac, I can check it tonight.
>
> Regards,
> Joe
>
> On Thu, Feb 9, 2017 at 10:59 AM, Otto Fowler 
> wrote:
>
>> 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 to ask, does anyone working on NiFi use a mac? The next problems I
>> have are not with .DS_Store files or anything ‘mac centric’, they are
> with
>> Nashorn Java script types in the ScriptingProcessor tests…..
>>
>> 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 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 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 workaround and I think we should resolve the issue.
>> > By looking at the usage of that method, such as DBCPConnectionPool, or
>> > JoltTransformJSON, those uses file name filter like this:
>> >
>> > (dir, name) -> name != null && name.endsWith(".jar")
>> >
>> > While filtering out specific .DS_Store works, targeting only name
>> > ending with .jar looks more generic work around.
>> >
>> > Would you mind open a JIRA and send a PR? I'd happy to review!
>> >
>> > Thanks,
>> > Koji
>> >
>> > On Thu, Feb 9, 2017 at 1:20 PM, Otto Fowler 
>> wrote:
>> >> 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 = "src/test/resources/TestClassLoaderUtils";
>> >> URL[] urls = ClassLoaderUtils.getURLsForClasspath(jarFilePath,
>> >> (dir,name)->name.compareTo(".DS_Store") == 0, false);
>> >> assertEquals(2, urls.length);
>> >> }
>> >>
>> >>
>> >> resolves the issue, and I am able to build everything.
>> >>
>> >>
>> >> On February 8, 2017 at 22:39:53, Otto Fowler (ottobackwa...@gmail.com)
>> >> wrote:
>> >>
>> >> 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 the DS_STORE is detected and has an url built and returned for
>> it.
>> >>
>> >> The test does not pass in a FileNamesFilter, which could be used to
>> filter
>> >> these files out I suppose.
>> >>
>> >> I am wondering if anyone is building successfully on Mac OS X?
>>

Re: Build failure on Mac OS X with DS_STORE files

[Otto Fowler]

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
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 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 patch *would* be?
>
>
> On February 9, 2017 at 11:11:55, Joe Skora (jsk...@gmail.com) wrote:
>
> 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 since I built on the Mac, I can check it tonight.
>
> Regards,
> Joe
>
> On Thu, Feb 9, 2017 at 10:59 AM, Otto Fowler 
> wrote:
>
>> 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 to ask, does anyone working on NiFi use a mac? The next problems
I
>> have are not with .DS_Store files or anything ‘mac centric’, they are
> with
>> Nashorn Java script types in the ScriptingProcessor tests…..
>>
>> 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 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 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 workaround and I think we should resolve the issue.
>> > By looking at the usage of that method, such as DBCPConnectionPool, or
>> > JoltTransformJSON, those uses file name filter like this:
>> >
>> > (dir, name) -> name != null && name.endsWith(".jar")
>> >
>> > While filtering out specific .DS_Store works, targeting only name
>> > ending with .jar looks more generic work around.
>> >
>> > Would you mind open a JIRA and send a PR? I'd happy to review!
>> >
>> > Thanks,
>> > Koji
>> >
>> > On Thu, Feb 9, 2017 at 1:20 PM, Otto Fowler 
>> wrote:
>> >> 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 = "src/test/resources/TestClassLoaderUtils";
>> >> URL[] urls = ClassLoaderUtils.getURLsForClasspath(jarFilePath,
>> >> (dir,name)->name.compareTo(".DS_Store") == 0, false);
>> >> assertEquals(2, urls.length);
>> >> }
>> >>
>> >>
>> >> resolves the issue, and I am able to build everything.
>> >>
>> >>
>> >> On February 8, 2017 at 22:39:53, Otto Fowler (ottobackwa...@gmail.com)

>> >> wrote:
>> >>
>> >> 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 the DS_STORE is detected and has an url built and returned
for
>> it.
>> >>
>> >> The test does not pass in a FileNamesFilter, which could be used to
>> filter
>> >> these files out I suppose.
>> >>
>> >> I am wondering if anyone is building successfully on Mac OS X?
>>

Re: Build failure on Mac OS X with DS_STORE files

[Otto Fowler]

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 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
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 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 patch *would* be?
>
>
> On February 9, 2017 at 11:11:55, Joe Skora (jsk...@gmail.com) wrote:
>
> 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 since I built on the Mac, I can check it tonight.
>
> Regards,
> Joe
>
> On Thu, Feb 9, 2017 at 10:59 AM, Otto Fowler 
> wrote:
>
>> 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 to ask, does anyone working on NiFi use a mac? The next problems I
>> have are not with .DS_Store files or anything ‘mac centric’, they are
> with
>> Nashorn Java script types in the ScriptingProcessor tests…..
>>
>> 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 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 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 workaround and I think we should resolve the issue.
>> > By looking at the usage of that method, such as DBCPConnectionPool, or
>> > JoltTransformJSON, those uses file name filter like this:
>> >
>> > (dir, name) -> name != null && name.endsWith(".jar")
>> >
>> > While filtering out specific .DS_Store works, targeting only name
>> > ending with .jar looks more generic work around.
>> >
>> > Would you mind open a JIRA and send a PR? I'd happy to review!
>> >
>> > Thanks,
>> > Koji
>> >
>> > On Thu, Feb 9, 2017 at 1:20 PM, Otto Fowler 
>> wrote:
>> >> 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 = "src/test/resources/TestClassLoaderUtils";
>> >> URL[] urls = ClassLoaderUtils.getURLsForClasspath(jarFilePath,
>> >> (dir,name)->name.compareTo(".DS_Store") == 0, false);
>> >> assertEquals(2, urls.length);
>> >> }
>> >>
>> >>
>> >> resolves the issue, and I am able to build everything.
>> >>
>> >>
>> >> On February 8, 2017 at 22:39:53, Otto Fowler (ottobackwa...@gmail.com)
>> >> wrote:
>> >>
>> >> 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 the DS_STORE is detected and has an url built and returned for
>> it.
>> >>
>> >> The test does not pass in a FileNamesFilter, which could be used to
>> filter
>> >> these files out I suppose.
>> >>
>> >> I am wondering if anyone is building successfully on Mac OS X?
>>

Re: Build failure on Mac OS X with DS_STORE files

[Otto Fowler]

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 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 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 workaround and I think we should resolve the issue.
> By looking at the usage of that method, such as DBCPConnectionPool, or
> JoltTransformJSON, those uses file name filter like this:
>
> (dir, name) -> name != null && name.endsWith(".jar")
>
> While filtering out specific .DS_Store works, targeting only name
> ending with .jar looks more generic work around.
>
> Would you mind open a JIRA and send a PR? I'd happy to review!
>
> Thanks,
> Koji
>
> On Thu, Feb 9, 2017 at 1:20 PM, Otto Fowler 
wrote:
>> 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 = "src/test/resources/TestClassLoaderUtils";
>> URL[] urls = ClassLoaderUtils.getURLsForClasspath(jarFilePath,
>> (dir,name)->name.compareTo(".DS_Store") == 0, false);
>> assertEquals(2, urls.length);
>> }
>>
>>
>> resolves the issue, and I am able to build everything.
>>
>>
>> On February 8, 2017 at 22:39:53, Otto Fowler (ottobackwa...@gmail.com)
>> wrote:
>>
>> 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 the DS_STORE is detected and has an url built and returned for
it.
>>
>> The test does not pass in a FileNamesFilter, which could be used to
filter
>> these files out I suppose.
>>
>> I am wondering if anyone is building successfully on Mac OS X?

Re: Build failure on Mac OS X with DS_STORE files

[Koji Kawamura]

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 (such as 1.8.0_31) is known to fail with some unit tests,
ensure to use the most recent version. The 0.x line works on Java 7 or
newer."
https://github.com/apache/nifi-site/blob/master/src/pages/markdown/quickstart.md#build-steps

I think it takes a while for the HTML web page gets synchronized.

On Sat, Feb 11, 2017 at 12:17 AM, Otto Fowler  wrote:
> 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 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 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 workaround and I think we should resolve the issue.
>> By looking at the usage of that method, such as DBCPConnectionPool, or
>> JoltTransformJSON, those uses file name filter like this:
>>
>> (dir, name) -> name != null && name.endsWith(".jar")
>>
>> While filtering out specific .DS_Store works, targeting only name
>> ending with .jar looks more generic work around.
>>
>> Would you mind open a JIRA and send a PR? I'd happy to review!
>>
>> Thanks,
>> Koji
>>
>> On Thu, Feb 9, 2017 at 1:20 PM, Otto Fowler 
>> wrote:
>>> 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 = "src/test/resources/TestClassLoaderUtils";
>>> URL[] urls = ClassLoaderUtils.getURLsForClasspath(jarFilePath,
>>> (dir,name)->name.compareTo(".DS_Store") == 0, false);
>>> assertEquals(2, urls.length);
>>> }
>>>
>>>
>>> resolves the issue, and I am able to build everything.
>>>
>>>
>>> On February 8, 2017 at 22:39:53, Otto Fowler (ottobackwa...@gmail.com)
>>> wrote:
>>>
>>> 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 the DS_STORE is detected and has an url built and returned for
>>> it.
>>>
>>> The test does not pass in a FileNamesFilter, which could be used to
>>> filter
>>> these files out I suppose.
>>>
>>> I am wondering if anyone is building successfully on Mac OS X?

Re: Build failure on Mac OS X with DS_STORE files

[Aldrin Piri]

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 
wrote:

> 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 (such as 1.8.0_31) is known to fail with some unit tests,
> ensure to use the most recent version. The 0.x line works on Java 7 or
> newer."
> https://github.com/apache/nifi-site/blob/master/src/
> pages/markdown/quickstart.md#build-steps
>
> I think it takes a while for the HTML web page gets synchronized.
>
> On Sat, Feb 11, 2017 at 12:17 AM, Otto Fowler 
> wrote:
> > 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 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 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 workaround and I think we should resolve the issue.
> >> By looking at the usage of that method, such as DBCPConnectionPool, or
> >> JoltTransformJSON, those uses file name filter like this:
> >>
> >> (dir, name) -> name != null && name.endsWith(".jar")
> >>
> >> While filtering out specific .DS_Store works, targeting only name
> >> ending with .jar looks more generic work around.
> >>
> >> Would you mind open a JIRA and send a PR? I'd happy to review!
> >>
> >> Thanks,
> >> Koji
> >>
> >> On Thu, Feb 9, 2017 at 1:20 PM, Otto Fowler 
> >> wrote:
> >>> 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 = "src/test/resources/TestClassLoaderUtils";
> >>> URL[] urls = ClassLoaderUtils.getURLsForClasspath(jarFilePath,
> >>> (dir,name)->name.compareTo(".DS_Store") == 0, false);
> >>> assertEquals(2, urls.length);
> >>> }
> >>>
> >>>
> >>> resolves the issue, and I am able to build everything.
> >>>
> >>>
> >>> On February 8, 2017 at 22:39:53, Otto Fowler (ottobackwa...@gmail.com)
> >>> wrote:
> >>>
> >>> 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 the DS_STORE is detected and has an url built and returned for
> >>> it.
> >>>
> >>> The test does not pass in a FileNamesFilter, which could be used to
> >>> filter
> >>> these files out I suppose.
> >>>
> >>> I am wondering if anyone is building successfully on Mac OS X?
>

Re: Build failure on Mac OS X with DS_STORE files

[Koji Kawamura]

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 be live.

--aldrin

On Fri, Feb 10, 2017 at 7:43 PM, Koji Kawamura 
wrote:

> 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 (such as 1.8.0_31) is known to fail with some unit tests,
> ensure to use the most recent version. The 0.x line works on Java 7 or
> newer."
> https://github.com/apache/nifi-site/blob/master/src/
> pages/markdown/quickstart.md#build-steps
>
> I think it takes a while for the HTML web page gets synchronized.
>
> On Sat, Feb 11, 2017 at 12:17 AM, Otto Fowler 
> wrote:
> > 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 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 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 workaround and I think we should resolve the issue.
> >> By looking at the usage of that method, such as DBCPConnectionPool, or
> >> JoltTransformJSON, those uses file name filter like this:
> >>
> >> (dir, name) -> name != null && name.endsWith(".jar")
> >>
> >> While filtering out specific .DS_Store works, targeting only name
> >> ending with .jar looks more generic work around.
> >>
> >> Would you mind open a JIRA and send a PR? I'd happy to review!
> >>
> >> Thanks,
> >> Koji
> >>
> >> On Thu, Feb 9, 2017 at 1:20 PM, Otto Fowler 
> >> wrote:
> >>> 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 = "src/test/resources/TestClassLoaderUtils";
> >>> URL[] urls = ClassLoaderUtils.getURLsForClasspath(jarFilePath,
> >>> (dir,name)->name.compareTo(".DS_Store") == 0, false);
> >>> assertEquals(2, urls.length);
> >>> }
> >>>
> >>>
> >>> resolves the issue, and I am able to build everything.
> >>>
> >>>
> >>> On February 8, 2017 at 22:39:53, Otto Fowler (ottobackwa...@gmail.com)
> >>> wrote:
> >>>
> >>> 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 the DS_STORE is detected and has an url built and returned for
> >>> it.
> >>>
> >>> The test does not pass in a FileNamesFilter, which could be used to
> >>> filter
> >>> these files out I suppose.
> >>>
> >>> I am wondering if anyone is building successfully on Mac OS X?
>

Re: Build failure on Mac OS X with DS_STORE files

[Otto Fowler]

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 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 
wrote:

> 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 (such as 1.8.0_31) is known to fail with some unit tests,
> ensure to use the most recent version. The 0.x line works on Java 7 or
> newer."
> https://github.com/apache/nifi-site/blob/master/src/
> pages/markdown/quickstart.md#build-steps
>
> I think it takes a while for the HTML web page gets synchronized.
>
> On Sat, Feb 11, 2017 at 12:17 AM, Otto Fowler 
> wrote:
> > 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 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 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 workaround and I think we should resolve the issue.
> >> By looking at the usage of that method, such as DBCPConnectionPool, or
> >> JoltTransformJSON, those uses file name filter like this:
> >>
> >> (dir, name) -> name != null && name.endsWith(".jar")
> >>
> >> While filtering out specific .DS_Store works, targeting only name
> >> ending with .jar looks more generic work around.
> >>
> >> Would you mind open a JIRA and send a PR? I'd happy to review!
> >>
> >> Thanks,
> >> Koji
> >>
> >> On Thu, Feb 9, 2017 at 1:20 PM, Otto Fowler 
> >> wrote:
> >>> 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 = "src/test/resources/TestClassLoaderUtils";
> >>> URL[] urls = ClassLoaderUtils.getURLsForClasspath(jarFilePath,
> >>> (dir,name)->name.compareTo(".DS_Store") == 0, false);
> >>> assertEquals(2, urls.length);
> >>> }
> >>>
> >>>
> >>> resolves the issue, and I am able to build everything.
> >>>
> >>>
> >>> On February 8, 2017 at 22:39:53, Otto Fowler (ottobackwa...@gmail.com)

> >>> wrote:
> >>>
> >>> 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 the DS_STORE is detected and has an url built and returned
for
> >>> it.
> >>>
> >>> The test does not pass in a FileNamesFilter, which could be used to
> >>> filter
> >>> these files out I suppose.
> >>>
> >>> I am wondering if anyone is building successfully on Mac OS X?
>