That is definitely not expected behaviour!
The rungui.cmd file has changed to try and better handle finding Java automatically, but it sounds as if something is going wrong on your system although it is not clear what! One way to find out might be to:
- open a command window
- change to the directory where calibre2opds has been installed
- use the RUNGUI command from within the command window. Progress messages should now be output as it tries to start up calibre2opds.
It may be easier to progress this by opening a issue at http://calibre2opds.myjetbrains.com/youtrack/issues
. That gives you an easy way to provide diagnostic information and for us to give suggestions.
The RUNGUI.cmd file does finish by trying to run "OpdsOutput-3.1-SNAPSHOT.jar", but it provides additional parameters such as setting the amount of RAM that Java should use. It is extremely strange that you can run this directly and not via the RUNGUI.cmd batch file.
One workaround might be to take the RUNGUI.cmd file from the 3.0 release and edit it in a text editor so the lines near the end that actually launches calibre2opds refer to 3.1 rather than 3.0. However I would like to get to the bottom of why the new RUNGUI.cmd file is failing on your system as otherwise it will keep failing in future releases.