Note that there are some explanatory texts on larger screens.

plurals
  1. POjava.io.FileNotFoundException: ~/play-2.1.1/framework/sbt/boot/update.log (No such file or directory)
    primarykey
    data
    text
    <p>I wrote a Puppet to install Play 2.1.1 on Virtual Machine running CentOS 6.2.</p> <p>The Puppet executed the following two commands:</p> <pre><code>/usr/bin/wget http://downloads.typesafe.com/play/2.1.1/play-2.1.1.zip /usr/bin/unzip play-2.1.1.zip </code></pre> <p>When I run <code>play</code> command inside the package, it shows the following error message:</p> <pre><code>java.io.FileNotFoundException: ~/play-2.1.1/framework/sbt/boot/update.log (No such file or directory) at java.io.FileOutputStream.open(Native Method) at java.io.FileOutputStream.&lt;init&gt;(FileOutputStream.java:209) at java.io.FileOutputStream.&lt;init&gt;(FileOutputStream.java:160) at java.io.FileWriter.&lt;init&gt;(FileWriter.java:90) at xsbt.boot.Update.&lt;init&gt;(Checks.java:51) at xsbt.boot.Launch.update(Launch.scala:275) at xsbt.boot.Launch$$anonfun$jnaLoader$1.apply(Launch.scala:120) at scala.Option.getOrElse(Option.scala:108) at xsbt.boot.Launch.jnaLoader$2f324eef(Launch.scala:115) at xsbt.boot.Launch.&lt;init&gt;(Launch.scala:94) at xsbt.boot.Launcher$.apply(Launch.scala:290) at xsbt.boot.Launch$.apply(Launch.scala:16) at xsbt.boot.Boot$.runImpl(Boot.scala:31) at xsbt.boot.Boot$.main(Boot.scala:20) at xsbt.boot.Boot.main(Boot.scala) Error during sbt execution: java.io.FileNotFoundException: ~/play-2.1.1/framework/sbt/boot/update.log (No such file or directory) </code></pre> <p>I didn't change a single line of code in the <code>play-2.1.1</code> directory. I googled around for the error message, but did not find any useful answer. Could anyone point out what is the problem?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload