[Issue 6501] Create dependencies between classes on import

http://argouml.tigris.org/issues/show_bug.cgi?id=6501






------- Additional comments from [email protected] Tue Dec 23 02:44:01 -0800 2014 -------
Thanks for continuing with this. I'll pull in the latest code and take a look
when I can. Possibly not till after the holiday period now (but maybe between
Christmas and new year).

I created issue 6503 - if that is tackled then it means that modellers can opt
not to generate the same level of detail.

As far as managing the created dependencies....

This is difficult to get right for all. If you are trying to model absolutely
everything in you application then maybe this can be done.

However an early design may have no classes and only a package design and their
planned dependencies. So it could be possible to have package dependencies with
no class dependencies. If creating a class dependency and then deleting it had a
side effect of deleting the package dependency then that may well not have been
the intention of the modeller.

I think this problem is where critics come in. A critic could spot that some
dependency between packages is implied by dependencies between classes and offer
to create that explicitly for you. Such a critic may already exist, if not we
can create a new issue for that.

------------------------------------------------------
http://argouml.tigris.org/ds/viewMessage.do?dsForumId=448&dsMessageId=3093283

To unsubscribe from this list, e-mail: [[email protected]].
Please do not reply to this mail. Instead, add your comments in the issue.