Details
Description
I found currently livy-core-parent, livy-repl-parent, livy-scala-api-parent are built individually, instead they are built in their child project. This leads 2 issues.
- Third party can not use livy-core_2.11 as maven dependency because it can not find its parent pom
- Code style check skip the code in parent project. e.g. The following import order is not correct, but we didn't detect it.
SparkRInterpreter.scala
import org.apache.commons.codec.binary.Base64 import org.apache.spark.{SparkConf, SparkContext} import org.apache.spark.util.{ChildFirstURLClassLoader, MutableURLClassLoader, Utils} import org.apache.commons.lang.StringEscapeUtils import org.json4s._ import org.json4s.JsonDSL._