Ever since 1.8.10 was release, I'm unable to run doxygen (under Windows) on anything with a PlantUML diagram. The same files will build without any problems using Doxygen v 1.8.9.1.
No matter what I do, or how the PATH enviroment variable is adjusted I still get:
error: Problems running PlantUML. Verify that the command 'java -jar "<somepath>\plantuml.jar" -h' works from the command line (where <somepath> is my path to PlantUML, not the actual text).
As other have notice, the command in itself runs from the command line without any problem.
Something changed between 1.8.9.1 and 1.8.10 that broke execution of Java from within doxygen (on Windows 7). The problem is actually worst on the Cygwin version of Doxygen (it prefixes the cygwin path of the running dir to the plantuml.jar path no matter the format).
Does anybody have any clue on how to fix this problem?
Or can I at least get a little clue on where the change happened so that I can manually fix the source code?
Any assistance will be greatly appreciated.
Last edit: Luis Vega 2016-02-02
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ever since 1.8.10 was release, I'm unable to run doxygen (under Windows) on anything with a PlantUML diagram. The same files will build without any problems using Doxygen v 1.8.9.1.
No matter what I do, or how the PATH enviroment variable is adjusted I still get:
error: Problems running PlantUML. Verify that the command 'java -jar "<somepath>\plantuml.jar" -h' works from the command line (where <somepath> is my path to PlantUML, not the actual text).
As other have notice, the command in itself runs from the command line without any problem.
Something changed between 1.8.9.1 and 1.8.10 that broke execution of Java from within doxygen (on Windows 7). The problem is actually worst on the Cygwin version of Doxygen (it prefixes the cygwin path of the running dir to the plantuml.jar path no matter the format).
Does anybody have any clue on how to fix this problem?
Or can I at least get a little clue on where the change happened so that I can manually fix the source code?
Any assistance will be greatly appreciated.
Last edit: Luis Vega 2016-02-02
Anybody knows a solution?
Any assistance will be greatly appreciated.