[GitHub] nifi issue #397: NIFI-1815

2017-02-14 Thread jdye64
Github user jdye64 commented on the issue: https://github.com/apache/nifi/pull/397 Unfortunately this isn't going to work due to license issues so closing. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project d

[GitHub] nifi issue #397: NIFI-1815

2017-02-14 Thread joewitt
Github user joewitt commented on the issue: https://github.com/apache/nifi/pull/397 I think we should close out this PR until licensing challenges are resolved and momentum is restored. It is certainly cool so even if we end up with a process that puts an abnormal burden on the user

[GitHub] nifi issue #397: NIFI-1815

2017-01-25 Thread jdye64
Github user jdye64 commented on the issue: https://github.com/apache/nifi/pull/397 @trixpan unfortunately I was unable to get this implementation to run properly when removing the libraries that had licensing conflicts. Its unfortunate but maybe we just need to close this issue since

[GitHub] nifi issue #397: NIFI-1815

2017-01-16 Thread trixpan
Github user trixpan commented on the issue: https://github.com/apache/nifi/pull/397 @jdye64 is the PR active or should we close it? Cheers --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not

[GitHub] nifi issue #397: NIFI-1815

2016-10-16 Thread trixpan
Github user trixpan commented on the issue: https://github.com/apache/nifi/pull/397 @olegz @jdye64 is this PR still active / plan to review? Cheers --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project