RE: [Wtp-wst-dev] Project granularity

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

RE: [Wtp-wst-dev] Project granularity

From: "Bjorn Freeman-Benson" <bjorn@xxxxxxxxxxxx>
Date: Mon, 1 Nov 2004 07:38:50 -0800
Delivered-to: wtp-wst-dev@xxxxxxxxxxx
Importance: Normal
List-archive: <http://dev.eclipse.org/pipermail/wtp-wst-dev/>
List-help: <mailto:wtp-wst-dev-request@eclipse.org?subject=help>
List-subscribe: <http://dev.eclipse.org/mailman/listinfo/wtp-wst-dev>, <mailto:wtp-wst-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <http://dev.eclipse.org/mailman/listinfo/wtp-wst-dev>, <mailto:wtp-wst-dev-request@eclipse.org?subject=unsubscribe>

Title: Message

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.

Follow-Ups:
- RE: [Wtp-wst-dev] Project granularity
  - From: David M Williams
- RE: [Wtp-wst-dev] Project granularity
  - From: Dave Carlson

References:
- RE: [Wtp-wst-dev] Project granularity
  - From: Dave Carlson

Prev by Date: RE: [Wtp-wst-dev] Project granularity
Next by Date: RE: [Wtp-wst-dev] Project granularity
Previous by thread: RE: [Wtp-wst-dev] Project granularity
Next by thread: RE: [Wtp-wst-dev] Project granularity
Index(es):
- Date
- Thread

Breadcrumbs