Could you prefix 'extra-options'?

[sebastiaansamyn-tc]

When adding SbtMultiJvm.multiJvmSettings to the settings of my project I get the following error:

[error] Some keys were defined with the same name but different types: 'extra-options' (sbt.Task[scala.collection.Seq[java.lang.String]], scala.Function1[java.lang.String, scala.collection.Seq[java.lang.String]])
[error] Use 'last' for the full log.

The issue is that the extra-options key is not only defined by sbt-multi-jvm, but also by another project. The other project is also not under my own control, so I have no way of using your plugin.

Wouldn't it be a good idea to prefix your keys and not use something as generic as "extra-options"?

[ktoso]

Thanks for reporting, I'll have a look at this!
You're most likely right - we should be using (key in ...) I think. I'll investigate more once the sun rises :-)

[2m]

We should increase the scope of this ticket to go through all of the keys and make sure they have multiJvm prefix or remove keys altogether if they duplicate the meaning of the keys that are already in sbt. More info #39 (comment)