title: Project-specific SBT JVM options
body: <p>For a project, I need to start <em>SBT</em> with specific <em>JVM</em> options (<code>-Dfile.encoding=UTF-8</code> and a number of memory/gc options) - but I don't necessarily want to apply those same options to every SBT project I have.</p>
  
  <p>I've seen references (in <em><a href="https://github.com/paulp/sbt-extras" rel="noreferrer">sbt-extras</a></em>) to the <code>.sbtopts</code> (project-specific <em>SBT</em> command line options) and <code>.jvmopts</code> (project-specific <em>SBT JVM</em> options) files that are supposed to support this, if found in the root directory of an <em>SBT</em> project, but the standard <em>Windows</em> version of <em>SBT</em> (I'm using version <strong>0.13.1</strong>) seems to ignore them.</p>
  
  <p>(The <em>sbt-extras</em> approach appeals to me because, assuming that <code>.sbtopts</code> and <code>.jvmopts</code> are tracked in version control, there is zero <em>SBT</em> configuration required for people wishing to build the project.)</p>
  
  <p>Is there a current mechanism to specify project-specific <em>SBT</em> options that works cross platform?</p>
  
  <p><strong>UPDATE</strong>: Since I originally raised this question, <code>.sbtopts</code> and <code>.jvmopts</code> are now part of the standard <em>Linux</em> version of <em>SBT</em>, and <em>sbt-extras</em> is no longer required. However, the <em>Windows</em> version only supports <code>.jvmopts</code> and does not recognize <code>.sbtopts</code>.</p>