playframework / playframework/playframework

`~run` not working as expected with sbt 1.3.x

Open
#9,983 11 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

topic:dev-environment topic:sbt type:defect
Dominant language
Scala
Stars
12.6k
Forks
4k
Avg merge
2d 3h
Merged PRs (30d)
29

Description

Play Version

Play 2.8.0 with sbt 1.3.4

API

Scala

Operating System

Windows 10 Pro

JDK

openjdk version "11.0.5" 2019-10-15
OpenJDK Runtime Environment AdoptOpenJDK (build 11.0.5+10)
OpenJDK 64-Bit Server VM AdoptOpenJDK (build 11.0.5+10, mixed mode)

Expected Behavior
  1. git clone git@github.com:playframework/play-samples.git
  2. cd play-samples/play-scala-hello-world-tutorial/
  3. sbt
  4. ~run
  5. Make a change to source code
  6. Recompilation is triggered when files are changed
Actual Behavior

Recompilation is not triggered.

Refreshing the browser window (= making a request to the app) does trigger recompilation, but AFAIK this should happen already when files change.

Downgrading to sbt 1.2.8 makes triggered execution work again as expected. Triggered execution for the compile task works using any version of sbt I have tried, so this issue is only about the run command with sbt 1.3.x (on Windows).

I have tried different fileWatchService implementations but the issue persists.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in play-samples/play-scala-hello-world-tutorial and reproduce the reported ~run behavior on Windows with sbt 1.3.x. Compare it with sbt 1.2.8 and with triggered execution for compile, then verify that changing source files recompiles without a browser request.

Written by the indexing model from the issue text.

Assessment

Tech stack
scala
Domain
build-system
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.