Yes, this is possible. I thought we had it set up correctly before, but I'll take a look why it isn't working now.
With regard to another issue that you raised about the same patch, it is a requirement that anyone who adds a new method to the Model subsystem's API also add, at a minumum, a stub that throws a NotYetImplemented exception to each implementation. Currently we have two implementations - MDR & eUML. Tom On Fri, Apr 18, 2008 at 11:13 AM, Bob Tarling <[EMAIL PROTECTED]> wrote: > 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
