It's me again :)
Another bug/feature - when parser can't parse something (maybe my fault in code), it does not follow the standart procedure - logging exception to console and returning non-zero result. Instead jcf shows messagebox with error and again server builds may fail.
Thanks.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Well, it seems to happen only when parser "dies". So that it throws a hard AV exception.
I can't provide a file, cause I fixed it :). But I definitely remember that I/O exception (when file is busy or something) produced the same messagebox.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi.
It's me again :)
Another bug/feature - when parser can't parse something (maybe my fault in code), it does not follow the standart procedure - logging exception to console and returning non-zero result. Instead jcf shows messagebox with error and again server builds may fail.
Thanks.
Hm, it shouldn't do that. can you provide a sample input that causes this?
Well, it seems to happen only when parser "dies". So that it throws a hard AV exception.
I can't provide a file, cause I fixed it :). But I definitely remember that I/O exception (when file is busy or something) produced the same messagebox.