[Uml-devel] [Bug 131270] New: java import - associations not setup correctly, duplicate classes created
JP Fournier
jfournier121 at rogers.com
Sun Jul 23 23:50:44 UTC 2006
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.kde.org/show_bug.cgi?id=131270
Summary: java import - associations not setup correctly,
duplicate classes created
Product: umbrello
Version: unspecified
Platform: Slackware Packages
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
AssignedTo: umbrello-devel.kde.org
ReportedBy: jfournier121 rogers com
Version: svn - 565476 (using KDE KDE 3.5.0)
Installed from: Slackware Packages
Compiler: gcc 3.4.4
OS: Linux
When a java class is imported, the classes that the imported class needs are assumed to be in the default package. If the dependent classes are imported they left in the default package from the navigation trees point of view, but cannot be move to the correct package. As well, depending on the order that classes are importted more than one class might be created (one in the default package and one in the correct package). When this occurs usually the associations are against the class in the default package instead of against the class in the real package.
I will attempt to attach some "demo" classes to this bug report.
For example:
- import these classes: Pack2.java Pack3.java Pack4.java Pack5.java
- this results in Pack4 being placed in the default package and cannot be moved to the pack2 package
- import Pack1.java
- this results in the related classes placed in the default package even though they belong in their respective packages
- now import Pack2.java Pack3.java Pack4.java Pack5.java this results in am empty pack2 package
-import Pack7.java
-import Pack1.java
- this results in duplicate Pack7 classes the associations are against one of the Pack7s and the member variables are included in the other
More information about the umbrello-devel
mailing list