Martin Duhem 82152b8905 Don't hardcode existing relations in TextAnalysisFormat ... The previous implementation of TextAnalysisFormat contained the list of all the existing relations that sbt knew of, and used this information to write to and read from the disk the persisted analyses. In this knew implementation, TextAnalysisFormat gets from the Relations object what are the existing relations, and then persists them to disk. The previous situation was not optimal since it meant that, in order to add a new dependency kind, one had to modify both the Relations and TextAnalysisFormat. Using this new implementation, no change to TextAnalysisFormat is required whenever a new dependency kind is added.		2014-09-11 14:45:47 +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	Don't hardcode existing relations in TextAnalysisFormat	2014-09-11 14:45:47 +02:00
integration/src/main/scala/sbt/compiler	added scalariform	2014-05-01 12:50:07 -04:00
interface	Never inspect twice the same macro application	2014-08-18 09:22:16 +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