[SAMZA-779] Remove the dependency on JUnit from SamzaTaskManager

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.10.0
• Component/s: yarn
• Assignee: Jake Maes
• Reporter: Jake Maes
• Created: 28/Sep/15 23:13
• Updated: 30/Sep/15 00:53
• Resolved: 30/Sep/15 00:53

Description

Remove the dependency on JUnit, which shouldn't be in production code and in some environments, could be explicitly excluded and cause build errors.

Interestingly, gradle allowed the dependency even though we only ever add JUnit as a testCompile dependency. It looks like this is due to a transitive dependency.

Snippet from the command "./gradlew :samza-yarn:dependencies":
compile - Compile classpath for source set 'main'.
...
--- org.apache.zookeeper:zookeeper:3.3.4
+--- log4j:log4j:1.2.15 -> 1.2.17
--- jline:jline:0.9.94
--- junit:junit:3.8.1