sbt/compile
Grzegorz Kossakowski 78b0f485fa Add `compilations` field to `Analysis`.
We store `Seq[xsbt.api.Compilation]` in `Analysis`. Compilation are
being appended to sequence for every iteration of the incremental
compiler.

Note that `Compilation`s are never removed from the sequence unless
you start from scratch with empty `Analysis`. You can do that by using
sbt's `clean` command.

The main use-case for using `compilations` field is to determine how
many iterations it took to compilen give code. The `Compilation` object
are also stored in `Source` objects so there's an indirect way to recover
information about files being recompiled in every iteration.

Since `Analysis` is persisted you can use this mechanism to track entire
sessions spanning multiple `compile` commands.
2012-12-10 09:15:52 -05:00
..
api Follow source layout convention supported by Eclipse. 2012-12-07 10:27:08 -08:00
inc Add `compilations` field to `Analysis`. 2012-12-10 09:15:52 -05:00
integration/src/main/scala/sbt/compiler Follow source layout convention supported by Eclipse. 2012-12-07 10:27:08 -08:00
interface Follow source layout convention supported by Eclipse. 2012-12-07 10:27:08 -08:00
ivy/src/main/scala/sbt/compiler Follow source layout convention supported by Eclipse. 2012-12-07 10:27:08 -08:00
persist Add `compilations` field to `Analysis`. 2012-12-10 09:15:52 -05:00
src More cleanup of Scala version handling, including managedScalaInstance to control automatic 'scala-tool' configuration and dependencies. 2012-12-09 20:40:41 -05:00
NOTICE - Stuart's improvements to triggered execution 2010-07-05 12:53:37 -04:00