sbt/util/collection/src/test/scala
Dan Sanduleac 96c7864088 Add 2 derived settings tests:
1) non-default derived settings, if they produce anything, the settings
   they produce must supersede previous assignents (in the settings seq)
   to the same key.

2) even if a derived setting is scoped at a higher scope (e.g.
   ThisBuild) the settings it produces are scoped at the intersection of
   that (the defining) scope and the scope of the triggering dependency.

2 is particularly nice as it enables this behaviour:
    derive(b in ThisBuild := a.value + 1)
    a in project1 := 0
    // a could be defined in all projects
    ==>
    Now (b in project1).value == (a in project1).value + 1 == 1
    and similarly in all other projects
    all with a single derived setting
2014-05-01 03:11:22 +01:00
..
DagSpecification.scala update to ScalaCheck 1.11.0 2013-11-04 11:28:40 -05:00
KeyTest.scala forgot a test 2011-05-26 22:24:26 -04:00
LiteralTest.scala graph evaluator, rewrite, general updates 2010-06-07 08:53:21 -04:00
PMapTest.scala 2.10.0-M5, different arity generalization 2012-11-17 20:19:24 -05:00
SettingsExample.scala Improve SettingsExample to allow orthogonal scopes (like projects/tasks) at a certain nestIndex 2014-05-01 03:09:50 +01:00
SettingsTest.scala Add 2 derived settings tests: 2014-05-01 03:11:22 +01:00