When building rp-application.conf, also consider dependent subprojects

[cunei]

When assembling the rp-application.conf file, the current code
explores the jars in the dependencyClasspath and the unmanaged
resources of the current subproject.
This pull request also includes in the file the unmanaged resources
of the other sbt subprojects that are dependencies of the current
subproject.

See #148

[eed3si9n]

LGTM

[thomschke]

Please see lightbend/config#608 (comment) !!!

sbt-reactive-app uses array concatenations very intensive (for akka.library-extensions etc).

BEFORE your PR all rp-tooling.confs comes before the application.conf:

# akka-cluster-bootstrap
akka {
  library-extensions += "com.lightbend.rp.akkaclusterbootstrap.ClusterBootstrapAutostart"
}
# akka-management
akka {
  library-extensions += "com.lightbend.rp.akkamanagement.AkkaManagementAutostart"
}

...

# application.conf
akka = ${akka}${myapp.default.akka}{
}

So before your PR the runtime config contains all library-extensions because default value substitution runs later.

But now (with reverse order - include application.conf comes first), so the default value substitution comes first:

include "application.conf"

# akka-cluster-bootstrap
akka {
  library-extensions += "com.lightbend.rp.akkaclusterbootstrap.ClusterBootstrapAutostart"
}
# akka-management
akka {
  library-extensions += "com.lightbend.rp.akkamanagement.AkkaManagementAutostart"
}

That's why akka.library-extensions always contains ONE entry (the last defined).