Hello,
I have some good news and some bad news. The good news is that it is relatively easy to get your rule to be run. The bad news is the message that is printed isn't very friendly.
Using sbt, you can get the rule to be run by including it on the classpath of the build - the easiest way is to build it separately and either include the jar into project/lib or as a dependency in project/plugins.sbt. Then, including the class name in the scalastyle config will get the rule executed correctly. The reason you never got any error messages out is because it just ignores them for the minute.
However, the message that is produced will be incorrect:
[info] error file=blah.scala message=space.after.comment.message line=7 column=19
Scalastyle uses a lookup into a properties file for the message that is written. Currently it uses a ResourceBundle, and is restricted to a single file, so you can't add this into the jar that you're adding to project/lib. To fix this will require a change to the core library, probably to use typesafe config library instead of a resource bundle. This is on my list of things to do, but will get done quicker if you submit a PR.
BTW, if you want to just contribute the checker to the core, I'd accept it as well.
Thanks.
Matthew Farwell.