<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=ISO-8859-1">
<META content="MSHTML 6.00.6001.18294" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY text=#000000 bgColor=#ffffff>
<DIV><FONT face=Arial size=2>Splitting common:</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>We can move all plugins other than 5 mentioned to
trunk/jst folder as is. That will involve mimimal changes, including new
features definitions. However, if we want to keep to naming agreements and
rename plugins and packages, for example <FONT
size=2>org.jboss.tools.common.el.core -> org.jboss.tools.jst.el.core, then it
may be not good for the nearest release as involving major
changes.</FONT></FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Cleaning model:</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>For instance, EclipseResourceUtil lists in
code possible natures based on XModel (jsfnature, strutsnature). It really
does not need either to know or use concrete natures. But it needs to know that
some Eclipse project do has a nature based on XModel. This is easily solved by
new extension point 'xmodelnature' that will provide for given installation
available natures. </FONT></DIV>
<DIV><FONT face=Arial size=2>Next, 'options' section of XModel is heaped in one
file in common. I will think about its separation into components.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Slava</FONT></DIV>
<BLOCKQUOTE
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B>
<A title=max.andersen@redhat.com href="mailto:max.andersen@redhat.com">Max
Rydahl Andersen</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=scabanovich@exadel.com
href="mailto:scabanovich@exadel.com">Viacheslav Kabanovich</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Cc:</B> <A title=vyemialyanchyk@exadel.com
href="mailto:vyemialyanchyk@exadel.com">vyemialyanchyk@exadel.com</A> ; <A
title=external-exadel-list@redhat.com
href="mailto:external-exadel-list@redhat.com">Exadel List</A> ; <A
title=jbosstools-dev@lists.jboss.org
href="mailto:jbosstools-dev@lists.jboss.org">jbosstools-dev@lists.jboss.org</A>
</DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Thursday, September 10, 2009 4:05
PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [jbosstools-dev] "Hibernate
Configuration 3.0 XML Editor"</DIV>
<DIV><BR></DIV><BR>
<BLOCKQUOTE cite=mid:B555BF0B7F3045BE809E0B10C67CCC6A@GLORYPC type="cite">
<DIV><FONT face=Arial size=2>> <FONT face="Times New Roman" size=3>The
problem is that common isn't just common.</FONT></FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>I suggest to split common. "True" common will
contain only</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>org.jboss.tools.common</FONT></DIV>
<DIV>
<DIV><FONT face=Arial size=2>org.jboss.tools.common.model</FONT></DIV>
<DIV>
<DIV><FONT face=Arial size=2>org.jboss.tools.common.model.ui</FONT></DIV>
<DIV>
<DIV><FONT face=Arial size=2>org.jboss.tools.common.text.xml</FONT></DIV>
<DIV><FONT face=Arial size=2>part of <FONT face=Arial
size=2>org.jboss.tools.common.text.ext</FONT></FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>Other plugins may be moved to
org.jboss.tools.jst...</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>Or, may we physically leave plugins where they
are, but for build and installation purposes apply this logic separation
'virtually' by defining other set of
features?</FONT></DIV></DIV></DIV></DIV></BLOCKQUOTE>I say we move the plugins
that can be moved to where they belong.<BR><BR>Could you outline which changes
you would do ?<BR> <BR>
<BLOCKQUOTE cite=mid:B555BF0B7F3045BE809E0B10C67CCC6A@GLORYPC type="cite">
<DIV><FONT face=Arial size=2>Next, I will clean common.model from
unnecessary references using new extension points.</FONT></DIV>
<DIV> </DIV></BLOCKQUOTE>sounds good. Again, would like to know what this
involves ?<BR>
<BLOCKQUOTE cite=mid:B555BF0B7F3045BE809E0B10C67CCC6A@GLORYPC type="cite">
<DIV><FONT face=Arial size=2>As to what we have now, installing Hibernate
Tools + common will not add jsf, jsp, etc editors; and though common
includes some excessive knowledge of jsp, jsf, struts, it does not add any
functionality.</FONT></DIV></BLOCKQUOTE>Ok - I'll try again then
;)<BR><BR>/max </BLOCKQUOTE></BODY></HTML>