...
After you run 'sbt test', you'll notice a lib_manage
 directory has been created. This directory is created by sbt to hold all the dependencies of the project.
build.sbt
Use the below template for the build.sbt file:
Code Block |
---|
name := "dfdl-RFormat"
organization := "com.tresys"
version := "0.0.1"
scalaVersion := "2.11.8"
crossPaths := false
testOptions in ThisBuild += Tests.Argument(TestFrameworks.JUnit, "-v")
resolvers in ThisBuild += "NCSA Sonatype Releases" at "https://opensource.ncsa.illinois.edu/nexus/content/repositories/releases"
libraryDependencies in ThisBuild := Seq(
"junit" % "junit" % "4.11" % "test",
"com.novocode" % "junit-interface" % "0.10" % "test",
"edu.illinois.ncsa" %% "daffodil-tdml" % "2.0.0-SNAPSHOT" % "test"
) |
Eclipse ID
If you organize your DFDL schema project using the above conventions, and then run 'sbt compile', the lib_managed directory will be populated. Then if you create a new Eclipse scala project from the directory tree, Eclipse will see the lib_managed directory and construct a classpath containing all those jars.
...