Hi Justin!

The nifi-parent artifact is a part of the current release you're voting on.
you'll have to build the proposed artifacts in the following order:

* nifi-parent
* nifi-nar-maven-plugin
* nifi

For each of the first two, you'll need to follow their respective README on
building but use the maven "install" phase in order to ensure the resultant
artifacts are installed in your local repo.

On Sat, May 16, 2015 at 10:19 PM, Justin Mclean <justinmcl...@me.com> 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 (
> http://repo.maven.apache.org/maven2) 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 apache.org email. The signatures is
> fine (and perhaps it's just me) but I‘m less likely to trust something
> signed with “nam...@hotmail.com” 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: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


-- 
Sean

Reply via email to