https://bugs.kde.org/show_bug.cgi?id=373382
--- Comment #2 from Ralf Habacker <ralf.habac...@freenet.de> --- The problem is that the importer creates UMLClassifier objects on any unknown parsed type e.g. at parsing setEnum(Test.AnEnum.ValueA) it creates an UMLClassifier AnEnum in the package Test. On parsing the real definition (in test.java) later it tries to use the UMLClassifier as UMLEnum which fails. In version 2.15.3 the type mismatch let umbrello completly ignore importing the enum which is not better. Note: A similar issue related to importing an object which turns out later to be a package has been fixed with bug 336012. -- You are receiving this mail because: You are watching all bug changes.
