RE: [Wtp-wst-dev] Project granularity

[David M Williams <david_williams@xxxxxxxxxx>]

I don't know what you mean by "Can
we create a design rule" but
you can open  bugs/feature requests on designs that you think wrong.

I know our 'sse.core' is one violator,
and the last think dragging us a long was FormatStrategy (I think) from
base Eclipse (which should have been a core 
object all along but ..... We've entered
bugs we we see such things and I just heard to day a model side "format
stratgy" is being worked on as we
speak. I think there's very view cases
where someone just made a simple mistake ... in most cases I know of, there
was some contraint with other code that 
required to break this obvious rule.
So, we'll just work through them all, one by one. 

David

"Bjorn Freeman-Benson" <bjorn@xxxxxxxxxxxx>
Sent by: wtp-wst-dev-admin@xxxxxxxxxxx

11/01/2004 10:38 AM

Please respond to
wtp-wst-dev

To	<wtp-wst-dev@xxxxxxxxxxx>
cc
Subject	RE: [Wtp-wst-dev] Project granularity

I have to agree that no "core"
plug-in should ever include a "ui" plug-in.
Another question/observation:
 Can we create a design rule for use of *.core vs *.ui plug-ins?  Does
such a rule exist for the Eclipse platform?  I see several *.core
plug-ins that include one or more org.eclipse.ui.* plug-ins.  This
seems wrong.  My understanding of the *.core is that it should run
in a headless platform configuration with no UI.