[ 
https://issues.apache.org/jira/browse/MINIFI-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16881398#comment-16881398
 ] 

Nenad Nikolic commented on MINIFI-504:
--------------------------------------

[~aldrin] thanks for responding so quickly!

I've submitted PR [#161|https://github.com/apache/nifi-minifi/pull/161] which 
makes the build green again. Granted, it took two failed attempts to submit the 
correct PR but in the end it worked out. :P 

I'd like to contribute, so I hope you can this PR to master. 
After this hopefully happens, I will rebase and resubmit my fix for MINIFI-478.

p.s. Only after finishing the work I searched MINIFI Jira project again to 
realize that there were already not one but two issues related to 
commons-daemon upgrade - MINIFI-502 and MINIFI-503. Sorry for not realizing 
this before and for creating another issue which is now linked to my green PR. 
:)

> Upgrade commons-deamon to 1.2.0 to make build green again
> ---------------------------------------------------------
>
>                 Key: MINIFI-504
>                 URL: https://issues.apache.org/jira/browse/MINIFI-504
>             Project: Apache NiFi MiNiFi
>          Issue Type: Bug
>          Components: Build
>    Affects Versions: 0.6.0
>            Reporter: Nenad Nikolic
>            Priority: Blocker
>             Fix For: 0.6.0
>
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> After submitting the [PR #158|https://github.com/apache/nifi-minifi/pull/158] 
> for a broken test (and underlying class) I realized the build breaks for an 
> unrelated reason. The reason was {{commons-daemon}} version 1.1.0 being used 
> which is not available on the 
> [mirror|https://apache.claz.org/commons/daemon/binaries/windows/] anymore.
> Currently, there's only one, newer version 1.2.0 hosted on the mirror that 
> should be used instead.
> Because of this issue with the build system it's not possible to submit any 
> correct PRs at the moment, so I've set the priority to Blocker.
> This Jira issue is FYI as another PR to upgrade {{commons-deamon}} to 1.2.0 
> is coming right up.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to