luke
/
sbt
mirror of https://github.com/sbt/sbt.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Warn when ignoring previous analysis for various reasons. 

This can confuse users and is hard to debug. It seems better to be
explicit about why we're choosing not to do an incremental compile.
This commit is contained in:
Benjy 2015-03-17 23:55:25 +00:00
parent 7113559d91
commit b70345c61b
1 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
compile/integration/src/main/scala/sbt/compiler/AggressiveCompile.scala
View File

@ -149,9 +149,12 @@ class AggressiveCompile(cacheFile: File) {
// previous Analysis completely and start with empty Analysis object
// that supports the particular value of the `nameHashing` flag.
// Otherwise we'll be getting UnsupportedOperationExceptions
log.warn("Ignoring previous analysis due to incompatible nameHashing setting.")
Analysis.empty(currentSetup.nameHashing)
case Some(previous) if equiv.equiv(previous, currentSetup) => previousAnalysis
case _ => Incremental.prune(sourcesSet, previousAnalysis)
case _ =>
log.warn("Pruning sources from previous analysis, due to incompatible CompileSetup.")
Incremental.prune(sourcesSet, previousAnalysis)
}
IncrementalCompile(sourcesSet, entry, compile0, analysis, getAnalysis, output, log, incOptions)
}