title: simplify settings for deb only build with sbt native packager
body: <p>I am trying to package my scala main app code as a .deb file. the app will only run on an ubuntu machine, so I do not really care about windows etc.</p>
  
  <p>Currently, I am struggling to find the most easiest way to compile the .deb using the simpliest settings. Let's assume I have a simple <code>object Kernel extends App</code> scala file in my <code>src</code> folder that should be bundled inlcuding the jardependencies.</p>
  
  <p>my current scala based debian settings for the project are:</p>
  
  <pre><code>import com.typesafe.sbt.SbtNativePackager._
  import NativePackagerKeys.
  
  
    val debSettings = mapGenericFilesToLinux ++ linuxSettings ++ debianSettings ++ Seq( 
      name in Debian := "my-app",
      version in Debian := "0.1-version",
      mainClass := Some("Kernel"),
      packageSummary := "",
      target := new java.io.File("target"),
      packageDescription := "my app",
      packageDescription := "my app desciption",
      NativePackagerKeys.normalizedName := "normalizedName",
      maintainer := "my name",
      sourceDirectory := new java.io.File("./src"),
      debianPackageDependencies in Debian ++= Seq("openjdk-7-jre"),
      debianPackageRecommends in Debian ++= Seq(),
      linuxPackageMappings in Debian ++= Seq() ,
      debianMaintainerScripts ++=Seq())
  </code></pre>
  
  <p>the <code>debian:package-bin</code>call  works and a deb is created but no binaries/jars are copied into the deb so i'm obviously missing some configuration. i know that there are still missing linuxPackageMappings etc but i'm wondering if there is an easier configuration for the compilation? using <code>packageArchetype.java_server</code> forces me to include so many not-used variables for windows etc. I want to avoid this.</p>
  
  <p><strong>Any suggestion how to simplify the settings + mappings for a deb-only build?</strong></p>