Problems running PlantUML since Doxygen 1.8.10 (Windows)

"Vega, Luis A" <[email protected]>
Newsgroups gmane.text.doxygen.general
Message-ID <[email protected]>
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 "<path>\plantuml.jar" -h' works from the command line (where <path> 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.

Note:
I use an environment variable to configure the location of the PlantUML jar-file since hardcoding would require all users to have direct access to the path. Here is an example:

PLANTUML_JAR_PATH = $(PLANTUML_HOME)/plantuml.jar

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140

_______________________________________________
Doxygen-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/doxygen-users
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.