Sparx Systems Forum

Enterprise Architect => Bugs and Issues => Topic started by: qwerty on April 13, 2018, 12:51:00 am

Title: Log file from XMI import
Post by: qwerty on April 13, 2018, 12:51:00 am
There's a check mark "Write Log File" in the XMI import dialog. Fine! But where the hell is that log written???

q.
Title: Re: Log file from XMI import
Post by: Nizam on April 13, 2018, 10:30:11 am
From the help
Quote
.
The log file is saved in the directory from which the file is being imported, with the same name as that of the imported file plus the suffix _ import.log.
Title: Re: Log file from XMI import
Post by: qwerty on April 13, 2018, 03:44:46 pm
You are right. I overlooked that since the im-/export dialog restricts display to .xm* files (as an Apple user I'm used to see other files greyed out; hum - Windoze). Anyway, the log just tells me that everything is find while the import croaks with an error. And after close/open EA everything is imported. Time for a new bug report :-/

q.
Title: Re: Log file from XMI import
Post by: Paolo F Cantoni on April 13, 2018, 04:39:44 pm
You are right. I overlooked that since the im-/export dialog restricts display to .xm* files (as an Apple user I'm used to see other files greyed out; hum - Windoze). Anyway, the log just tells me that everything is find while the import croaks with an error. And after close/open EA everything is imported. Time for a new bug report :-/

q.
Sparx has a conceptual problem with "logs".  They obviously didn't didn't watch Startrek (especially series 1).  Logs are to be written in real time and with a timestamp.  Otherwise, they aren't logs!  (That's why the show is interrupted with the log (to make the log)).

Paolo
Title: Re: Log file from XMI import
Post by: qwerty on April 13, 2018, 06:43:17 pm
Yep. Like they have no test department. Or someone to design a useful GUI. Sigh. Let's see what my bug report brings in return. I suspect "It's a feature, not a bug".

q.
Title: Re: Log file from XMI import
Post by: qwerty on April 19, 2018, 07:00:52 pm
I imported the XMI with ArgoUML and that immediately showed where the culprit with my XMI was. No (further) comment.

q.