I'm not really sure if the description below refers to a bug or simply to some misunderstanding from my side. Anyway...

Apparently, you cannot pass an action involving a sub-module which otherwise would be perfectly valid if you call SBT via command line. For example, you could call this line below from command line:

$ sbt MyModule/test

... whilst an equivalent configuration from the plugin does not recognizes the action to be performed, as shown below:

{{sbt launcher: sbt-0.13.11
JVM Flags:
sbt Flags: -Dsbt.log.noformat=true
Actions: MyModule/test}}

It complains saying:

{{[error] Expected ID character
[error] Not a valid command: MyModule
[error] Expected project ID
[error] Expected configuration
[error] Expected ':' (if selecting a configuration)
[error] Expected key
[error] Not a valid key: MyModule
[error] MyModule/test
[error] }}

Please let me know if I did something wrong, which is something I suppose I did.

Thanks a lot,

--Richard Gomes