Re: [VOTE] Release Apache NiFi 0.1.0-incubating
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
Re: [VOTE] Release Apache NiFi 0.1.0-incubating
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
Re: [VOTE] Release Apache NiFi 0.1.0-incubating
Justin, 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. [1] http://mail-archives.apache.org/mod_mbox/incubator-nifi-dev/201505.mbox/%3cCALJK9a6XO=4RgjejACOd=dqG_AFoJb14AKAxWTm52Q=b53w...@mail.gmail.com%3e On Sat, May 16, 2015 at 11: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
Re: [VOTE] Release Apache NiFi 0.1.0-incubating
On Sat, May 16, 2015 at 10:19 PM, Justin Mclean justinmcl...@me.com wrote: -The value of the scm tag (nifi-0.1.0-incubating-rc13”) in the pom file may be incorrect. SCM tag looks present to me: https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;a=tag;h=b10fad4171d965f78db8ea0976acdad769a207b9 Would be nice if the tag pointed to a 'release' tag, but I get how that might be harder for the project to do. -- Sean
Re: [VOTE] Release Apache NiFi 0.1.0-incubating
Justin, First, thanks for attempting to validate the release. You will need to build all three components mentioned above in order. The error you note suggests that the nifi-parent was not built before attempting the build of nifi-0.1.0. We expect most releases to be much easier to validate than this one but we needed to factor out a common parent here to share across the other two modules. Our preference would be to have a single build that does it all but that isn't possible when one of the artifacts you want to build would also be an extension/plugin you'd use in maven in that same build. Regarding the email address used we will be sure to better reflect that in our release guide. The .zip is generated by the 'apache-release' profile that comes from the standard org.apache/apache/16 artifact. It uses a 'apache-source-release-assembly-descriptor' which only generates a zip. We could extend that but I'd be reluctant to. Thanks Joe On Sat, May 16, 2015 at 11: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 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache NiFi 0.1.0-incubating
On Sat, May 16, 2015 at 10:41 PM, Joe Witt joe.w...@gmail.com wrote: Regarding the email address used we will be sure to better reflect that in our release guide. The .zip is generated by the 'apache-release' profile that comes from the standard org.apache/apache/16 artifact. It uses a 'apache-source-release-assembly-descriptor' which only generates a zip. We could extend that but I'd be reluctant to. This particular issue is addressed in version 17 of the apache parent pom[1]. [1]: https://issues.apache.org/jira/browse/MPOM-47 -- Sean
Re: [VOTE] Release Apache NiFi 0.1.0-incubating
Hi, Changing my vote to +1 (binding). Sorted the compile issue out, code now compiles and tests pass. Sorry for the noise. The readme has been updated since the released version and that along with the replies here provided the answer. [1] Thanks, Justin 1.https://github.com/apache/incubator-nifi/blob/develop/README.md - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache NiFi 0.1.0-incubating
Hi, Would be nice if the tag pointed to a 'release' tag, but I get how that might be harder for the project to do. That's what I would of expected. It's a very minor issue and up to the project if they want to change that or not in future releases. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
