blob: 37ff351b4572b1c27f83604cd1bfe5e8329d1036 [file] [log] [blame]
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<meta
http-equiv="Content-Type"
content="text/html; charset=iso-8859-1">
<title>org.eclipse.wst.command.env.core</title>
<link
rel="stylesheet"
type="text/css"
href="../sources/formate.css">
</head>
<body>
<p class="ueberschrift">What Is The Common Component?</p>
<p>Actually, its three components &ndash; wst.common, jst.common,
wst.command</p>
<p><em>&quot;The common components contain plugins that provide generic
functionality that are applicable in several different contexts. Plugins
in the common component should not have dependencies on plugins outside
of the Eclipse base.&rdquo;</em></p>
<p>Some conceptual tests to decide what should go into common&hellip;</p>
<ul>
<li>Is it destined for API ?
<ul>
<li>if it has no API story, its should be moved into a different
component specific to those who need it</li>
</ul>
</li>
<li>Should it ultimately live in base Eclipse ?
<ul>
<li>common is often used as a temporary staging ground for generic
function that will eventually be absorbed into base Eclipse</li>
</ul>
</li>
<li>What are the dependencies?
<ul>
<li>if the function has dependencies on more than base eclipse,
that&rsquo;s a red flag that it might not be &lsquo;common&rsquo;</li>
</ul>
</li>
<li>Is it generic?
<ul>
<li>Is this function generically applicable to multiple domains in
practice (not just theory</li>
</ul>
</li>
</ul>
<p class="ueberschrift">Development - WTP 1.0</p>
<ul>
<li>One of our main goals in the common area is to ?Work with the
platform? to help integrate existing frameworks delivered by both
projects.
<ul>
<li>Common Navigator (Move down to Platform/UI in 3.2)</li>
<li>Undoable commands (Integrate, and push down requirements)</li>
<li>Converged environment / command / data frameworks</li>
<li>Flexible Projects (Integrate, Drive requirements)</li>
<li>Logical resources (Integrate)</li>
<li>Tabbed properties sheet (Move down)</li>
</ul>
</li>
</ul>
<p class="ueberschrift">Common - Evolution</p>
<ul>
<li>Existing plugins may migrate to base Eclipse (or other projects)</li>
<ul>
<li>tabbes properities sheet</li>
<li>project navigator</li>
</ul>
<li>Existing plugins may not be 'common' enough
<ul>
<li>in practice function is less 'common' than we initial thought...
who's actually using it?</li>
</ul>
</li>
</ul>
<p>We need to collectively scrutinize the 'common' components to rnsure
things lives in the right place</p>
<p class="ueberschrift">Plugins - Dependencies</p>
<ul>
<li>Eclipse
<ul>
<li>Platform
<ul>
<li>JDT,Resource</li>
</ul>
</li>
<li>JEM
<ul>
<li>Java Model (Reflective EMF Model)</li>
<li>EMF Extensions (Shared by JEM and WTP)
<ul>
<li>Project scoped Resources</li>
<li>RefResource</li>
</ul>
</li>
</ul>
</li>
<li>EMF
<ul>
<li>Primary metamodel framework</li>
<li>EMF.edit</li>
</ul>
</li>
</ul>
</li>
</ul>
<p class="ueberschrift">API<a name="API"></a> - Status</p>
<ul>
<li>Provisional API
<ul>
<li>Flexible Project API</li>
<li>Validation</li>
<li>Data model wizard/commands</li>
<li>Environment framework</li>
<li>Common Navigator</li>
</ul>
</li>
<li>Internal frameworks
<ul>
<li>EMF extensions ? base function shared with JEM to be pushed to
EMF</li>
<li>Proposed API is relatively young</li>
</ul>
</li>
</ul>
<p class="ueberschrift">Bugzilla - Queries</p>
<ul>
<li>Query for wst.common, wst.validation:
<ul>
<li><a
href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&amp;product=Web+Tools&amp;component=wst.
common&amp;component=wst.validation&amp;bug_status=NEW&amp;bug_status=ASSIGNED&amp;bug_status=REOPENED">wst.common;
wst.validation </a></li>
</ul>
</li>
<li>Query for wst.command:
<ul>
<li><a
href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&amp;product=Web+Tools&amp;component=wst.command&amp;bug_status=NEW&amp;bug_status=ASSIGNED&amp;bug_status=REOPENED">wst.command</a></li>
</ul>
</li>
</ul>
<br>
<br>
</body>
</html>