documentation for Build.scala files

[fommil]

In the docs http://www.scala-sbt.org/sbt-native-packager/archetypes/java_app/index.html enablePlugins(JavaAppPackaging) is recommended. But this only works for build.sbt style projects. what is the correct magic for Build.scala style projects?

[muuki88]

AFAIK AutoPlugins only work with build.sbt files together. There is no way I know to get around this (yet). I know this is a pain when migrating from Build.scala builds to *.sbt builds :(

cc @jsuereth

[fommil]

So support for .scala style projects is deprecated?

[fommil]

by fiddling around, I've worked out that adding this at the top

import com.typesafe.sbt.packager.archetypes.JavaAppPackaging
import JavaAppPackaging.autoImport._

and this to a module

  enablePlugins (
    JavaAppPackaging
  )

seems to allow me to type stage. And the keys seem to be available (but I cannot confirm if they work).

[kardapoltsev]

You could take a look here example of Build.scala with autoplugins and some additional configuration

[muuki88]

I'm not sure if *.scala is deprecated (though it gets more and more discouraged).

[muuki88]

@fommil I would close this as at this point we have no way to solve this?

[fommil]

This is just an RFE for better documentation, I'm sure that can be fixed... although whether it will be fixed is another question.

[muuki88]

Actually I'm pretty happy, when Build.scala will go away. As a beginner I was really confused, when to use what and why. Still I can understand the issue, when a project is heavily relying on this and all of a sudden you will have to change anything.

[fommil]

I will kick up a massive fuss if they try to remove Build.scala. It's the only thing that (vaguely) makes any sense to me... the .sbt files are total voodoo and completely useless if you want to do anything non-standard.

[muuki88]

I will close this ticket for now as "how to use Build.scala with AutoPlugins" is as an SBT concern and not sbt-native-packager. Feel free to provide a PR, when there are docs available.