DOC: Describe mergeStrategy for multi-node testing
Reported in mailinglist.
To move from multi-jvm testing to multi-node testing one of the first things I needed to do was to modify "mergeStrategy in assembly" that the sbt-multi-jvm plugin uses. This wasn't something I readily knew how to do and this will probably come up often enough that this ought be included in the multi-node-testing documentation, I dont often have to modify sbt keys that are scoped by both Task and Config.
This is the code I used to tweak the mergeStrategy from my project's config files:
To move from multi-jvm testing to multi-node testing one of the first things I needed to do was to modify "mergeStrategy in assembly" that the sbt-multi-jvm plugin uses. This wasn't something I readily knew how to do and this will probably come up often enough that this ought be included in the multi-node-testing documentation, I dont often have to modify sbt keys that are scoped by both Task and Config.
This is the code I used to tweak the mergeStrategy from my project's config files:
mergeStrategy in (MultiJvm,assembly) <<= (mergeStrategy in (MultiJvm,assembly)) { (old) =>
{
case "logback.xml" => MergeStrategy.first
case "play.plugins" => MergeStrategy.concat
case x => old(x)
}
}
Leave a comment