title: Heroku webapp-runner --enable-naming
body: <p>I've been facing with a combersome task: deploying a spring project ( using JNDI ). </p>
  
  <p>Right now the problem is related to the webapp-runner option "enable-naming". 
  My datasources are declared by jndi - using tomcar context.xml.
  When i feed webapp-runner with the option referred i get this message:</p>
  
  <pre><code>Exception in thread "main" com.beust.jcommander.ParameterException:   
  **Unknown option: --enable-naming** 
  at com.beust.jcommander.JCommander.parseValues(JCommander.java:723)
  at com.beust.jcommander.JCommander.parse(JCommander.java:275)
  at com.beust.jcommander.JCommander.parse(JCommander.java:258)
  at com.beust.jcommander.JCommander.(JCommander.java:203)
  at webapp.runner.launch.Main.main(Main.java:74)
  </code></pre>
  
  <p>I've been digging the webapp-runner code and saw this condition:</p>
  
  <pre><code>if (commandLineParams.enableNaming ||
  commandLineParams.enableBasicAuth ||
  commandLineParams.tomcatUsersLocation != null) {
  tomcat.enableNaming();
  }
  </code></pre>
  
  <p>So i've tried with --enable-basic-auth option and my app runs just fine... The problem is i don't want basic-auth in my site.</p>
  
  <p>I'm using maven heroku-maven-plugin, and as
  WEBAPP_RUNNER_OPTS: --context-xml tomcat-heroku-server-conf/context.xml --enable-naming</p>
  
  <p>Thanks in advance.</p>