Skip to content

Failure to use jar file produced by 'scala -savecompiled'  #15180

Closed
@lilyevsky

Description

@lilyevsky

Compiler version 3.1.2

If I use 'scala -savecompiled ....' when running a scala script, it properly produces the jar file. It is expected that on the second run it would use that jar file in order to speed up execution, but it is not happening.

I clearly see this by timing the execution: in my example the run using scala runner always takes around 7 seconds, while direct run using 'java -jar ...' takes less than 0.5 seconds.

As a workaround, I wrote a shell script that compares files timestamps and based on that decides how to run the script.

According to http://www.mit.edu/afs.new/sipb/project/scala/scala/scala-2.10.0/doc/tools/scala.html , this feature used to work before in 2.10 version.

Related documentation issue: if I run 'scala --help', I don't even see any mentioning of '-savecompile'. So I wonder what is the story here - maybe this feature is not yet fully implemented?

Metadata

Metadata

Assignees

No one assigned

    Labels

    itype:bugstat:needs triageEvery issue needs to have an "area" and "itype" label

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions