nifi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Aldrin Piri <>
Subject Re: nifi error
Date Sat, 25 Jul 2015 22:21:58 GMT

I was not able to recreate the issue you are experiencing (this is on OS X
and CentOS 7) from the latest version of development and starting with an
empty maven repository on each.

If the folder is not being created, it seems like it may be hitting an
issue with permissions.  I see you are using Vagrant.  Is it possible the
folder you are mapping into your Vagrant environment is not getting the
appropriate UID/GID?

To inspect things on your end, evaluate a listing of the checkout directory
in your Vagrant environment:

ls -la of the nifi directory checkout
id (to show your users and groups)

Additionally, as the user executing the build, are you able to manually
create the target directory?

On Sat, Jul 25, 2015 at 2:32 PM, sagar gaikwad <> wrote:

> Hey Joe,
> I was running into similar error as Dattu . I followed your steps
> git checkout develop
> Please be sure to build in the following order:
> cd ./nifi-parent
> mvn clean install
> I run into a different error while trying to build nifi-nar-maven-plugin
> mvn clean install
> Error Start :
> Failed to execute goal
> org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process
> (default)
> on project nifi-nar-maven-plugin:Error finding remote resources manifests:
> /home/vagrant/nifi/nifi-nar-maven-plugin/target/maven-shared-archive-resources/META-INF/NOTICE
> Error End:
> I noticed that the TARGET directory is not created in the nar folder. Also
> noticed the relative path in the POM file was not set up. It was throwing
> NIFI project not found error. I fixed that to point it to the parent
> directory and now I am getting the above-stated error.
> Sagar Gaikwad
> --
> View this message in context:
> Sent from the Apache NiFi (incubating) Developer List mailing list archive
> at

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message