[Uml-devel] [Bug 283744] Junk residual artifacts littering project file

[Oliver Kellogg]

https://bugs.kde.org/show_bug.cgi?id=283744


Oliver Kellogg <okellogg at users.sourceforge.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |okellogg at users.sourceforge.
                   |                            |net




--- Comment #6 from Oliver Kellogg <okellogg users sourceforge net>  2012-02-04 23:39:34 ---
Hi Kip,

(In reply to comment #5)
> [...]
> Do you want me to apply your latest patch to svn head, recompile, open your
> edited project file, resave, and then try exporting the diagrams again and
> watch for warnings on the console to see if they are still there?

I've not yet arrived at that point - I'm just going through your file, writing
down my observations, and trying to fix stuff as I progress.
The patch that I attached is not essential to the diagram export.

As written in comment #5,
> 
> The next step would be to grep for all references to the "undef" datatype:
> 
>   $ grep '"A7B42ow89qzr"' Engine_without_undef_generalizations.xmi
> 
> and decide how to change those references to something sensible.

I'm afraid this step is manual work. Apparently some older Umbrello version has
mangled a few objects into the "undef" datatype.
Unfortunately Umbrello does not have a feature like "show usages" (of a given
object - the old Rational Rose had this btw) and so I believe sticking to the
XMI file is the only way to fix these references.

> I've been using Umbrello and building from source daily for a long time now and
> that may be why there is some older junk in the project file which may be
> relics or fingerprints of older versions of Umbrello.

Ah, that might explain why I have problems reconstructing what went wrong while
looking at the current trunk code.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.