You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@nifi.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2015/11/13 02:41:11 UTC

[jira] [Commented] (NIFI-1134) Fix the ExecuteCommand tests to not use seemingly arbitrary jars

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

ASF subversion and git services commented on NIFI-1134:
-------------------------------------------------------

Commit 02102ea1c2add14df874744633f2f6dcd83d3525 in nifi's branch refs/heads/master from [~joewitt]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=02102ea ]

Revert "NIFI-1134".  This was removed because they looked like floating classes.  But in reality they are used to make jars which we use to test the build.  However, we really need the test to work differently but until that is fixed these must stay.

This reverts commit 41f3875347a6ff7c87e35665019c35e99e78eecb.


> Fix the ExecuteCommand tests to not use seemingly arbitrary jars
> ----------------------------------------------------------------
>
>                 Key: NIFI-1134
>                 URL: https://issues.apache.org/jira/browse/NIFI-1134
>             Project: Apache NiFi
>          Issue Type: Task
>          Components: Extensions
>            Reporter: Joseph Witt
>            Priority: Trivial
>
> This thread explains the situation.  We need to fix the tests to not depend on such artifacts or at least if we do we need it to build them on the fly first.  And really these tests just need to be fixed.
> http://mail-archives.apache.org/mod_mbox/nifi-dev/201511.mbox/%3CCA%2BLyY54w-32Z02L-Q5G9xJ6SqQegU2EuPgtdHmHyiHpN0h31dg%40mail.gmail.com%3E



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)