[ https://issues.apache.org/jira/browse/APEXMALHAR-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vlad Rozov updated APEXMALHAR-2306: ----------------------------------- Description: 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 OperatorContext interface or we should find other ways to eliminate this kind of dependency. was: 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. > 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 OperatorContext interface or we should > find other ways to eliminate this kind of dependency. -- This message was sent by Atlassian JIRA (v6.3.4#6332)