[EMAIL PROTECTED] wrote: you should never have duplicate dependencies .. this will result in duplicate code.. hance the compilation errors (end of quote)
Doh! I did have only one dependency modelled, but MagicDraw left another relation hanging around in my package. Might it be an idea to have the model checked on "unused" relations, or as I encountered before, unused action-states. Maybe this can be presented to the user by means of warnings, as long as MagicDraw does not provided the functionality to validate the model this might circumvent some strange errors (which are, I have to admit, caused by sloppy behaviour). _________________________________________________________ Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=3652#3652 Posting to http://forum.andromda.org/ is preferred over posting to the mailing list! ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Andromda-user mailing list Andromda-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/andromda-user
