Carles,
I haven't played with this particular plugin. However, approach I've used for workarounding other plugins' issues could help here as well.
So the approach is to create a wrapper script. That could be bash, for example, on Linix/Mac or bar on Windows. Use this wrapper in plugin settings as main executable.
With this approach you can gain full flexibility - you can pass whatever parameters you want and so on. NetBeans may (and most likely will) pass some parameters to that script (depending on plugin). That is quite easy to debug.
Here is an example of such wrapper in bash, written for PHPUnit:
#!/bin/bash
#
localInputFile=${7:4}
localJUnitLog=$2
localCoverageLog=$4
remoteInputFile=`echo $localInputFile | sed "s|$localPath|$remotePath|g"`
remoteJUnitLog=${remotePath}nb-phpunit-log.xml
remoteJUnitLoginLocalFilePath=${localPath}nb-phpunit-log.xml
remoteCoverageLog=${remotePath}nb-phpunit-coverageClover.xml
remoteCoverageLoginLocalFilePath=${localPath}nb-phpunit-coverageClover.xml
remoteCoverageLoginLocalFilePathNew=${remoteCoverageLoginLocalFilePath}new
ssh root@<remote-server> "phpunit --colors --log-junit $remoteJUnitLog --coverage-clover $remoteCoverageLog $remoteInputFile"
cp $remoteJUnitLoginLocalFilePath $localJUnitLog
sed "s|$remotePath|$localPath|g" $remoteCoverageLoginLocalFilePath > $remoteCoverageLoginLocalFilePathNew
cp $remoteCoverageLoginLocalFilePathNew $localCoverageLog
This one I've used to force PHPUnit NetBeans plugin to use phpunit not at localhost, but at the remote server. But what you need here is the way parameters are caught. You could debug that doing just
echo $0 $1 $2
and opening output window in Netbeans to see the result.
Hope this would help.