RE: [RDT-Dev] Source structure (correction)

[Chris W. <cwi...@ro...>]

> On Wednesday 05 January 2005 20:15, David Corbin wrote:
> > Out of curiosity, why is RDT structured with so many different
plugins?
> > Surely having an average of 11 java files per plugin means there's a
lot
> > mroe overhead for plugin management.
> 
> Sorry, I made a mistake.  It's not 11, it's about 43.  It still seems
to
> that
> there are an awful lot of projects (not all are plugins), several with
> just
> one package of java files,
> 
> ...rdt.tests.all - one java file
> ...rdt.ri - three java files, two packages
> ...rtd.launching - 10 java files, one package
> 
> (that's just a sampling).  The question still holds -  why is it
> structured
> like this?

The tests have always been split out separate from the actual plugins -
so that doubles our module count right there.

Second, the ri plugin is brand new. It will likely be merged into the ui
plugin.

Third there's actually not much overhead involved in "managing" plugins,
so creating another one really doesn't add much work at all. Its just a
matter of adding an entry to the feature to include it.

And lastly, I know I've been trying to emulate the structure that JDT
uses in determining what gets its own plugin. Hence the testunit plugin
separated, or the launching.

Thanks,
Chris