Using Def.derive with configuration-scoped tasks can break task aggregation

[smarter]

Consider the following build.sbt (git repo: https://github.com/smarter/sbt-derive-bug):

val foo = taskKey[Unit]("")
val bar = taskKey[Unit]("")

lazy val a = (project in file("a")).
  settings(
    foo in Compile := {
      println("foo in a")
    }
    //,
    // Def.derive(bar := {
    //   val _ = foo.value
    // })
  )

lazy val root = (project in file(".")).
  aggregate(a).
  settings(
    foo in Compile := {
      println("foo in root")
    }
  )

foo is aggregated in root, as expected:

> root/foo
foo in root
foo in a

But now, if we uncomment the commented lines above, we get:

> root/foo
foo in root

This happens with both sbt 0.13 and 1.0. This does not happen if we use bar in Compile := ... instead of Def.derive, or if we replace all foo in Compile by foo.
This makes sbt-dotty unusable with aggregated projects without manually disabling the IDE plugin: scala/scala3#3172

[smarter]

This makes sbt-dotty unusable with aggregated projects without manually disabling the IDE plugin: scala/scala3#3172

Worked around by not using Def.derive: scala/scala3#3178

[jvican]

I am not able to reproduce this behavior with sbt +1.3.0. It looks like this issue was fixed in some commit between 1.2.8 and 1.3.0.