RE: [Wtp-wst-dev] Project granularity

["Dave Carlson" <dcarlson@xxxxxxxxxxxxxxx>]

Title: Message

After a bit more poking around, I see that org.eclipse.wst.sse.core requires org.eclipse.jface.text (which in turn requires org.eclipse.swt).  Although not a .ui plugin, I would expect a .core project to be independent of SWT presentation.  I'm interested in a headless configuration of WTP with a web-based UI for team collaboration.

 

Dave

-----Original Message-----
From: wtp-wst-dev-admin@xxxxxxxxxxx [mailto:wtp-wst-dev-admin@xxxxxxxxxxx] On Behalf Of Bjorn Freeman-Benson
Sent: Monday, November 01, 2004 8:39 AM
To: wtp-wst-dev@xxxxxxxxxxx
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.