The patch on defect 1009 surprised me in that it contained references to classes in the MDR project such as import org.omg.uml.foundation.core.Interface;
That used to be restricted by our project dependencies allowing only knowledge of the model interface from the main application. The current plugin dependancies allows access into both MDR and eUML though. Is that because these are both compile time and runtime dependencies? Is there any way to restrict this any further to enforce encapsulation of the model implementation within eclipse? If not then can JDepend help us at least enforce this restriction by failing a test? Bob. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
