<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
<br>
Max Rydahl Andersen wrote:
<blockquote cite="mid:4A7AB724.1020208@redhat.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
The JBDS global icon is just when we don't have any other options - and
using that should be limited<br>
and it should not be done in a way so we create large dependencies.
Copy it over is ok for this.<br>
<br>
Afaik, we did get an icon created specifically for ESB (<a
moz-do-not-send="true"
href="https://jira.jboss.org/jira/browse/JBIDE-3040">https://jira.jboss.org/jira/browse/JBIDE-3040</a>
?) - we should use that<br>
and if that isn't big enough get one done that are.<br>
<br>
btw. the big problem here is that common/xmodel drags a *massive* set
of dependencies in...we<br>
really need to fix that since if we had that under control we could
actually have proper shared resources<br>
<br>
</blockquote>
<br>
As first step we have to split richfaces to separate features and
approach could be to have tree features:<br>
<br>
A feature with the plug-ins those are a dependencies of XModel:<br>
<br>
org.jboss.tools.common.feature<br>
org.jboss.tools.common<br>
org.jboss.tools.common.kb<br>
org.jboss.tools.common.gef<br>
<br>
A XModel feature <br>
<br>
org.jboss.tools.common.model.feature<br>
org.jboss.tools.common.model<br>
org.jboss.tools.common.model.ui<br>
org.jboss.tools.common.text.ext<br>
org.jboss.tools.common.text.xml<br>
<br>
All others plug-ins that depends on XModel<br>
<br>
org.jboss.tools.common.framework.feature<br>
org.jboss.tools.common.verification.*<br>
org.jboss.tools.common.projecttemplates<br>
org.jboss.tools.common.el.*<br>
org.jboss.tools.common.resref.*<br>
org.jboss.tools.jst.*<br>
org.jboss.tools.jsf.*<br>
org.jboss.tools.vpe.*<br>
<br>
That means if ESB depends on XModel only <br>
org.jboss.tools.common.feature<br>
org.jboss.tools.common.model.feature<br>
would be installed as dependencies<br>
<br>
Since we are going to get rid of separate archives on download site an
use archived update site <br>
there should be no problems for user, required features would be
detected trough dependencies.<br>
<br>
<br>
That's a separate discussion how to split it and fix all cyclic
references.<br>
<br>
Here is tentative list of features (I know that not just that simple
because there are several cyclic dependencies):<br>
<br>
org.jboss.tools.common.feature<br>
org.jboss.tools.common<br>
org.jboss.tools.common.kb<br>
org.jboss.tools.common.gef<br>
<br>
org.jboss.tools.common.model.feature<br>
org.jboss.tools.common.model<br>
org.jboss.tools.common.model.ui<br>
org.jboss.tools.common.text.ext<br>
org.jboss.tools.common.text.xml<br>
<br>
org.jboss.tools.common.verification.feature<br>
org.jboss.tools.common.verification<br>
org.jboss.tools.common.verification.ui<br>
<br>
org.jboss.tools.common.projecttemplates.feature<br>
org.jboss.tools.common.projecttemplates<br>
<br>
org.jboss.tools.common.el.feature<br>
org.jboss.tools.common.el.*<br>
<br>
org.jboss.tools.common.resref.feature<br>
org.jboss.tools.common.resref.*<br>
<br>
org.jboss.tools.jsf.fetaure<br>
org.jboss.tools.jsf.*<br>
<br>
org.jboss.tools.jst.feature<br>
org.jboss.tools.jst.*<br>
<br>
org.jboss.tools.vpe.feature<br>
org.jboss.tools.vpe.*<br>
<br>
This is not a plan, just a suggestion for discussion.<br>
<br>
Denis<br>
</body>
</html>