ASF GitHub Bot commented on APEXMALHAR-2306:

GitHub user sanjaypujare opened a pull request:


    APEXMALHAR-2306  fix OperatorContext implementations to add the new 
required method

    @vrozov   these changes were required to run malhar successfully against 
latest apex-core. This is just for review for now

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/sanjaypujare/apex-malhar 

Alternatively you can review and apply these changes as the patch at:


To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #459
commit 7d106b4abd42dcf4e9e7bf54a63eb042bcdc32bb
Author: Sanjay Pujare <san...@datatorrent.com>
Date:   2016-10-18T23:35:35Z

    fix OperatorContext implementations to add the new required method


> malhar unit test(s) have a dependency on OperatorContext in apex-core
> ---------------------------------------------------------------------
>                 Key: APEXMALHAR-2306
>                 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2306
>             Project: Apache Apex Malhar
>          Issue Type: Bug
>          Components: test benches
>            Reporter: Sanjay M Pujare
> While trying to build/test malhar against the latest apex-core, the following 
> failure was noticed
> .../apex-malhar/library/src/test/java/com/datatorrent/lib/helper/OperatorContextTestHelper.java:[47,17]
>  com.datatorrent.lib.helper.OperatorContextTestHelper.TestIdOperatorContext 
> is not abstract and does not override abstract method getName() in 
> com.datatorrent.api.Context.OperatorContext
> Ideally malhar should mock up the OperstorContext interface or we should find 
> other ways to eliminate this kind of dependency.

This message was sent by Atlassian JIRA

Reply via email to