sbt/compile
Grzegorz Kossakowski f7c00ab581 Sketch of abstracting over dependency details in incremental compiler
This represents a sketch of the idea that we can abstract over details
of a specific dependency kind. The goal would that only a few
implementations of methods in incremental would be sensitive to specific
dependency kind:

  1. Dependency extraction logic
  2. Implementation of Relations which adds dependencies to specific
     relations (or abstract over specific relations)
  3. Invalidation algorithm (Incremental.scala) which has different
     of each kind of dependency
  4. TextAnalysisFormat

In particular, adding a new dependency kind would not affect signatures
of existing methods.

What needs to be done:

  - finish refactoring so the code compiles again and previous semantics
    are preserved
  - introduce deprecated overloads that preserve old method signatures
    (this is required for preserving binary compatibility)
2014-09-12 08:52:06 +02:00
..
api Bump expected 2.11 module versions so we can compile with 2.11 2014-05-14 19:08:05 -04:00
inc Sketch of abstracting over dependency details in incremental compiler 2014-09-12 08:52:06 +02:00
integration/src/main/scala/sbt/compiler added scalariform 2014-05-01 12:50:07 -04:00
interface Fix SOE with macros in dependencies extraction 2014-09-10 15:54:06 +02:00
ivy/src/main/scala/sbt/compiler added scalariform 2014-05-01 12:50:07 -04:00
persist Don't hardcode existing relations in TextAnalysisFormat 2014-09-11 14:45:47 +02:00
src/main/scala/sbt added scalariform 2014-05-01 12:50:07 -04:00
NOTICE - Stuart's improvements to triggered execution 2010-07-05 12:53:37 -04:00