Re: [dali-dev] Test plugins

[Paul Fullbright <paul.fullbright@xxxxxxxxxx>]

According to our rather lengthy discussion today, it seems we have 
settled on the following:


1) The component 'Dali' will have no subcomponents and, as such, will 
retain its existing plugin structure.
   org.eclipse.dali.utility
   org.eclipse.dali.db (dependency on *.utility)
   org.eclipse.dali.core (dependency on *.utiltity and *.db)
   org.eclipse.dali.edit (dependency on *.core)
   org.eclipse.dali.ui (dependency on all above)
  
We debating pulling *.db and/or *.utility code into the *.core plugin 
and pulling the *.edit code into either the *.core or *.ui plugins, but 
decided against for the following reasons:
      - *.db should be separate from *.core in order to shield .*core 
from any rdb/dtp code.
      - *.utility should be separate from *.core to prevent circular 
references between *.core and *.db.
      - *.ui should be separate on general principles
      - We don't clearly know where *.edit would better be placed.

We also debated renaming *.utility and *.db to *.core.utility and 
*.core.db but decided against as it was needless, there being no concept 
of dali subcomponents.


2) Test plugins shall follow the observed convention of naming and not 
the stated convention.
   org.eclipse.dali.utility.tests
   org.eclipse.dali.db.tests
   org.eclipse.dali.core.tests
   org.eclipse.dali.ui.tests

We debating using the stated convention of naming 
(org.eclipse.dali.tests.*) but decided against due to the lack of 
observed obedience and because it better describes what each test plugin 
is testing.

We also debated rolling the utility and db tests into the core test 
plugin, but decided against since db tests may require further 
dependencies that we don't want to require of core test developers and 
to maintain test->plugin clarity.


Committers:  PLEASE RESPOND if you have any objections.

Thanks,
- Paul