Hello Remi,
Thanks for the feedback. First off, I'd like to say if you have any suggestions for improving the plugin, please let me know!
As for JS Test Driver itself, it definitely does not need to have Maven support as has already been proven by the fact that it works as-is today. One of the problems people have had with JS Test Driver not being Mavenized is you are more limited as to what libraries JS Test Driver itself uses when resolving conflicts. Normally, you can tell Maven to exclude dependencies if there is a conflict, but as of now we aren't able to do so as they are folded into one monolithic JS Test Driver jar file. Again, there are potential ways to work around this, but, in a Maven environment, everything just seems to work together better if it follows the same conventions.
Thanks again, I hope you find use in the updated plugin!
Nathan