The sbt distributions used in sbtenv-install have md5 sums but sbtenv-install is only able to handle sha1 sums.

Ideally, sbtenv-install should check downloaded tarballs against their md5 sums.

the oshinko-webui tooling currently defaults to exposing a route to the spark master ui when a cluster is created. the clusters created automatically by the source-to-image tooling do not. should the default behavior of exposing this route be consistent across all deployment methodologies?

Wanted to notify you of a really strange issue I ran into and my fix. I was using the following Dockerfile for a simple multi-stage SBT build:

FROM bigtruedata/sbt AS build
WORKDIR /app
COPY . .
RUN sbt assembly

FROM openjdk:8-alpine
COPY --from=build /app/target/scala-2.12/app.jar /app/app.jar
EXPOSE 8080
ENTRYPOINT ["java", "-jar", "/app/app.jar"]

Which, after all the bu

README example is obsolete for latest SBT version:

Run style check before compilation

Add the following sbt settings:

compile in Compile <<= (compile in Compile) dependsOn (jcheckStyle in Compile)
compile in Test <<= (compile in Test) dependsOn (jcheckStyle in Test)

Working configuration:

Compile / compile := (Compile / compile).dependsOn(Compile / jcheckStyle).val