Known Issues and Limitations
- The source code cannot be manipulated through the diagram.
This means that changing or deleting a classifier or relationship
within a diagram has no effect on the source code.
This is intentional.
- Opening a class diagram with many classifiers or dropping a classifier
onto a freshly opened class diagram with many other classifiers can take
a little longer. This is because the reverse engineering of relationships
requires the complete parsing of every classifier. The second time a
classifier is dropped on the diagram, it should be nearly instantaneous.
- Drag and drop does not work from the Navigator in the Resource perspective.
- Attributes in binary classifiers from JARs do not have default/initial
values because those are parsed from the source code.
- Currently the Eclipse refactoring extension points do not support
everything you can actually do in the Java IDE. For example, the move of
inner classes or non-static class members via drag and drop does not
trigger the refactoring extension points. Such operations therefore cause
the deletion of the affected classifiers and associations from class
diagrams.
- When you rename a type and select the option 'Update similarly named
variables and methods', any associations related to renamed variables are
lost since Eclipse doesn't provide a notification.
- When a classifier is open in an editor and the 'Link with Editor' button
in the Package Explorer is enabled, you cannot drag that classifier from
the Package Explorer onto a diagram because as soon as you select the
classifier, its editor will be brought to the foreground. Simply turn off
the 'Link with Editor' button to keep the diagram in the foreground. The
Type Hierarchy view has similar behavior, but that can only be turned off
by closing the editor.
- When you change the classpath of a Java project, unavailable classes
will only disappear from diagrams after a restart of Eclipse.