Still cannot get sbt 0.9.7 running on win

25 views
Skip to first unread message

Vasil Remeniuk

unread,
May 18, 2011, 3:29:39 AM5/18/11
to simple-build-tool
Hello,

    I still cannot get sbt 0.9.7 running on win7. Falls with the exception below:

[info] Set current project to default (in build file:/C:/Users/Vasil_Remeniuk/.sbt/plugins/)
java.lang.RuntimeException: Could not update last modified time for file C:\Users\Vasil_Remeniuk\.sbt\plugins\target\streams
\$global\$global\streams\$global\out
        at scala.Predef$.error(Predef.scala:58)
        at sbt.IO$.touch(IO.scala:82)
        at sbt.std.Streams$$anon$3$$anon$2.make(Streams.scala:89)
        at sbt.std.Streams$$anon$3$$anon$2.text(Streams.scala:79)
        at sbt.std.Streams$$anon$3$$anon$2.log(Streams.scala:84)
        at sbt.std.TaskStreams$class.log(Streams.scala:30)
        at sbt.std.Streams$$anon$3$$anon$2.log(Streams.scala:68)
        at sbt.Project$.installGlobalLogger(Project.scala:296)
        at sbt.Project$.updateCurrent(Project.scala:144)
        at sbt.Project$.setProject(Project.scala:134)
        at sbt.BuiltinCommands$$anonfun$loadProjectImpl$2.apply(Main.scala:351)
        at sbt.BuiltinCommands$$anonfun$loadProjectImpl$2.apply(Main.scala:346)
        at sbt.Command$$anonfun$applyEffect$1$$anonfun$apply$2.apply(Command.scala:61)
        at sbt.Command$$anonfun$applyEffect$1$$anonfun$apply$2.apply(Command.scala:61)
        at sbt.Command$$anonfun$applyEffect$2$$anonfun$apply$3.apply(Command.scala:63)
        at sbt.Command$$anonfun$applyEffect$2$$anonfun$apply$3.apply(Command.scala:63)
        at sbt.Command$.process(Command.scala:91)
        at sbt.MainLoop$$anonfun$next$1$$anonfun$apply$1.apply(Main.scala:71)
        at sbt.MainLoop$$anonfun$next$1$$anonfun$apply$1.apply(Main.scala:71)
        at sbt.State$$anon$1.process(State.scala:54)
        at sbt.MainLoop$$anonfun$next$1.apply(Main.scala:71)
        at sbt.MainLoop$$anonfun$next$1.apply(Main.scala:71)
        at sbt.ErrorHandling$.wideConvert(ErrorHandling.scala:13)
        at sbt.MainLoop$.next(Main.scala:71)
        at sbt.MainLoop$.run(Main.scala:62)
        at sbt.xMain.run(Main.scala:32)
        at xsbt.boot.Launch$.run(Launch.scala:54)
        at xsbt.boot.Launch$$anonfun$explicit$1.apply(Launch.scala:43)
        at xsbt.boot.Launch$.launch(Launch.scala:68)
        at xsbt.boot.Launch$.apply(Launch.scala:14)
        at xsbt.boot.Boot$.runImpl(Boot.scala:24)
        at xsbt.boot.Boot$.main(Boot.scala:15)
        at xsbt.boot.Boot.main(Boot.scala)
[error] java.lang.RuntimeException: Could not update last modified time for file C:\Users\Vasil_Remeniuk\.sbt\plugins\target
\streams\$global\$global\streams\$global\out

Thanks+regards,
Vasil
--
-----

Twitter: twitter.com/remeniuk
Blog: vasilrem.com
Github: github.com/remeniuk
Scala Enthusiasts Belarus: twitter.com/scalaby


Mark Harrah

unread,
May 18, 2011, 8:13:52 AM5/18/11
to simple-b...@googlegroups.com
On 5/18/11, Vasil Remeniuk <vasil.r...@gmail.com> wrote:
> Hello,
>
> I still cannot get sbt 0.9.7 running on win7. Falls with the exception
> below:

The exception indicates setting the last modified time fails. I don't
know why that only happens on windows. Perhaps the file is open and
linux allows you to set it when it is open but windows doesn't.
Either way, sbt doesn't need to set the last modified time there, so I
changed it to not do that.

-Mark

> --
> You received this message because you are subscribed to the Google Groups
> "simple-build-tool" group.
> To post to this group, send email to simple-b...@googlegroups.com.
> To unsubscribe from this group, send email to
> simple-build-t...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/simple-build-tool?hl=en.
>
>

Vasil Remeniuk

unread,
May 18, 2011, 8:16:31 AM5/18/11
to simple-b...@googlegroups.com
Great, thank you! Have just pulled the update.

--Vasil

Gustavo Hexsel

unread,
May 18, 2011, 10:29:19 AM5/18/11
to simple-b...@googlegroups.com
  File locks operate differently on Windows than on Linux, Linux being a lot more permissive about opening already-open files since we're basically using inodes after open (I think the directory inode is not kept locked).  

  Could be the cause for this...
Reply all
Reply to author
Forward
0 new messages