[jbosstools-dev] Any interest in splitting 'common' module up?

[Rob Stryker]

Hey All:

I'm just trying to get the ball moving on a possible breakup of the 
'common' module. Common is currently FULL of all sorts of different 
stuff. It has 23 plugins, 10 tests, and 13 features. Since we've just 
finished a major release, now is the time to discuss reorganizations. I 
hope I'm not stepping on anyone's toes. Even fi I don't end up doing the 
work, it's at least time to open the discussion.

Common simply has too many different things all bundled together, and a 
lot of them aren't "common" ;)  I tried to make an image of what all 
depends on what with regards to common, even going so far as to show 
what the different common plugins depend on, but that image was just too 
crowded, too many nodes. So for now I've made a more simple one of just 
INSIDE common.

Hopefully we can split things out into things that are truly common and 
many other plugins might use, vs stuff that's a little less common.

Attached is an image showing common's current interdependencies. Direct 
dependencies supplied by other plugins are not shown, to help make the 
graph easier to understand. (ex: org.jboss.tools.common.ui depends on 
o.j.t.common, but since o.j.t.c.ui depends on o.j.t.c.text.xml, that 
direct link is not shown.)

    Hopefully this graph will help us ask other questions, for example 
WHY does o.j.t.common.ui depend on o.j.t.c.text.xml, and would the code 
that is in common.ui be more appropriate to live in o.j.t.c.text.xml 
instead?

Anyway, we can at least start the discussion. Image attached.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: commonComponentStructure.png
Type: image/png
Size: 91916 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20120815/7b0199e5/attachment-0001.png