This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 102165 - Conversion of java-centric UML to regular and vice versa
Summary: Conversion of java-centric UML to regular and vice versa
Status: REOPENED
Alias: None
Product: uml
Classification: Unclassified
Component: Reverse Engineering (show other bugs)
Version: 5.x
Hardware: All All
: P2 blocker (vote)
Assignee: issues@uml
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-04-23 15:06 UTC by malcolmcarmen
Modified: 2007-04-24 01:19 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description malcolmcarmen 2007-04-23 15:06:08 UTC
I recently wanted to work on a java project, but wished to generate a
non-java-specific UML representation for it through use of the reverse
engineering feature. However, it appears that "regular" UML and java-centric are
quite distanced from each other. Ability to convert from one to the other would
be very useful. I'm not as UML savvy as I'd like to be, but it seems that this
would almost be entirely cosmetics-based -- it would be very nice to see it as a
project option, rather than seperating the two project types entirely.

Thanks!
Comment 1 Sergey Petrov 2007-04-23 15:34:45 UTC
I agree it should be an option for java based uml project, it seems similar
enhancement was missed during migration to issuezilla.
But separation of projects is still valid because java based project impose java
restrictions on uml module and there is only uml restrictions in independent uml
project
Comment 2 Trey Spiva 2007-04-23 15:50:48 UTC
Yes it would be very nice to right click on a few classes are a package in Java project to generate 
diagrams.  It would also be nice to have a UML information embedded directly into the Java project tree.  
Such as use cases, component diagram, sequence diagrams, etc.

I have marked this as a duplicate of issue 82140

*** This issue has been marked as a duplicate of 82140 ***
Comment 3 Sergey Petrov 2007-04-23 17:48:09 UTC
As I understand this issue is about "java" notation in java based uml
project/diagrams when user may want too see standard uml notation which is more
common then first one  and be able to use re/code gen/etc funtionality at the
same time.
Comment 4 malcolmcarmen 2007-04-24 01:19:44 UTC
Sorry, I should have made it a bit more clear to begin with -- sergeyp is
correct. I find little wrong with the java-based representation of UML (usage of
verbose modifiers such as "public" instead of "+", etc.), but it would certainly
be nice to go from java-centric notation to generic UML, and hopefully the other
way around (I'm not so sure that is possible).