mirror of
https://github.com/sbt/sbt.git
synced 2026-10-06 18:14:04 +02:00
Ethan Atkins
dcccd17fd2
@olegych reported in https://github.com/sbt/sbt/issues/4722 that sometimes even when a build was triggered during watch that no recompilation would occur. The cause of this was that we never invalidated the file stamp cache for managed sources or output files. The optimization of persisting the source file stamps between task evaluations in a continuous build only really makes sense for unmanaged sources. We make the implicit assumption that unmanaged sources are infrequently updated and generally one at a time. That assumption does not hold for unmanaged source or output files. To fix this, I split the fileStampCache into two caches: one for unmanaged sources and one for everything else. We only persist the unmanagedFileStampCache during continuous builds. The managedFileStampCache gets invalidated every time. I added a scripted test that simulates changing a generated source file. Prior to this change, the test would fail because the file stamp was not invalidated for the new source file content. Fixes #4722
sbt
sbt is a build tool for Scala, Java, and more.
For general documentation, see http://www.scala-sbt.org/.
sbt 1.x
This is the 1.x series of sbt. The source code of sbt is split across several Github repositories, including this one.
- sbt/io hosts
sbt.iomodule. - sbt/util hosts a collection of internally used modules.
- sbt/librarymanagement hosts
sbt.librarymanagementmodule that wraps Ivy. - sbt/zinc hosts Zinc, an incremental compiler for Scala.
- sbt/sbt, this repository hosts modules that implements the build tool.
Other links
- Setup: Describes getting started with the latest binary release.
- FAQ: Explains how to get help and more.
- sbt/sbt-zero-seven: hosts sbt 0.7.7 and earlier versions
Issues and Pull Requests
Please read CONTRIBUTING carefully before opening a GitHub Issue.
The short version: try searching or asking on StackOverflow.
license
See LICENSE.