incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Aldrin Piri <>
Subject Re: [VOTE] Release Apache NiFi 0.1.0-incubating
Date Sun, 17 May 2015 03:40:26 GMT

We had an additional email that went out to the NiFi dev listing providing
a guide in getting evaluating this release.  We have a few projects that
are utilized and require separate installation steps as some refactoring
occurred to introduce the nifi-parent.  Some of those details were not made
immediately clear in the release email, but are covered in the README with
the source bundle for the core nifi release.  Additionally, Joe Witt
provided an accompanying guide to the community,  available in the mailing
list archive [1].  In summary, the nifi-parent and nifi-nar-maven-plugin
must both be installed before the nifi build can be accomplished.   This
particular release is likely a bit of an outlier as the nifi-parent and
nifi-nar-maven-plugin should be fairly well set moving forward, but has led
to the issues in your evaluation process this time around.


On Sat, May 16, 2015 at 11:19 PM, Justin Mclean <> wrote:

> Hi,
> +0 (binding) as I’m unable to get the release to compile.
> This may be my setup or perhaps an issue with the pom.xml file. When
> trying to compile I get:
> The project org.apache.nifi:nifi:0.1.0-incubating
> (/Users/justinmclean/Downloads/ApacheNiFi/nifi-0.1.0-incubating/pom.xml)
> has 1 error
> [ERROR]     Non-resolvable parent POM: Could not find artifact
> org.apache.nifi:nifi-parent:pom:1.0.0-incubating in central (
> and 'parent.relativePath' points at
> no local POM @ line 18, column 13 -> [Help 2]
> Any ideas?
> Everything else looks good:
> - Signatures and hashes correct
> - DISCLAIMER exists
> - LICENSE and NOTICE correct (I doubled check all licenses - nice work!)
> - No unexpected binary files (although there are some binary test files)
> - All source files have headers
> A couple of very minor things:
> - Consider signing release with an email. The signatures is
> fine (and perhaps it's just me) but I‘m less likely to trust something
> signed with “” style email address. :-)
> - Consider releasing a .tar.gz package as well as a .zip package
> -Consider (but not required) adding “apache" to the artefact name.
> -The value of the scm tag ("nifi-0.1.0-incubating-rc13”) in the pom file
> may be incorrect.
> Thanks,
> Justin
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

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