checkonly flags do not log which file contains error

Question

Imagine you have 1000 files, and you want to check syntax of these :

$ java -jar /scripts/plantuml.jar `find . -name '*.iuml' | xargs` -teps -charset UTF-8 -graphvizdot `which dot` -v -checkonly

(0.000 - 81 Mo) 79 Mo - PlantUML Version 7991

(0.004 - 81 Mo) 79 Mo - GraphicsEnvironment.isHeadless() false

(0.009 - 81 Mo) 79 Mo - Setting current dir: .

(0.009 - 81 Mo) 79 Mo - Setting current dir: /Users/kenji/plantuml-bug/exitcode/.

(0.009 - 81 Mo) 79 Mo - Using charset UTF-8

(0.012 - 81 Mo) 79 Mo - Setting current dir: /Users/kenji/plantuml-bug/exitcode/.

(0.015 - 81 Mo) 79 Mo - Setting current dir: /Users/kenji/plantuml-bug/exitcode/.

Some diagram description contains errors

 

 

Okay, one (or more) of these 1000 iuml file contains error...

 

If I generate files, I got the information : 

 

$ java -jar /scripts/plantuml.jar `find . -name '*.iuml' | xargs` -teps -charset UTF-8 -graphvizdot `which dot` -v -failonerror

(0.000 - 81 Mo) 79 Mo - PlantUML Version 7991

(0.003 - 81 Mo) 79 Mo - GraphicsEnvironment.isHeadless() false

(0.008 - 81 Mo) 79 Mo - Setting current dir: .

(0.009 - 81 Mo) 79 Mo - Setting current dir: /Users/kenji/plantuml-bug/exitcode/.

(0.009 - 81 Mo) 79 Mo - Using charset UTF-8

(0.012 - 81 Mo) 79 Mo - Setting current dir: /Users/kenji/plantuml-bug/exitcode/.

(0.015 - 81 Mo) 79 Mo - Setting current dir: /Users/kenji/plantuml-bug/exitcode/.

(0.015 - 81 Mo) 79 Mo - Reading file: ./Temp.iuml

(0.563 - 81 Mo) 65 Mo - Creating file: /Users/kenji/plantuml-bug/exitcode/./Temp.eps

(1.524 - 81 Mo) 72 Mo - Number of image(s): 1

Error in file: /Users/kenji/plantuml-bug/exitcode/Temp.iuml

Some diagram description contains errors

 

 

Answer 1

Thanks for the report.
This is (should be?) fixed in the following beta:
https://dl.dropboxusercontent.com/u/13064071/plantuml.jar

Very few tests done, so please do feedback if needed.
 

Comments

Fixed for me (both in my current project and using the simple example used to reproduce the issue).

Edit :
I found a related issue : if error is inside of an included file, the error is reported to be in the including (maybe adding line indication for error in output could help to find that the "real" error is located in the included file).