Do we still need loading of legacy test plans?

[Jordi Salvat i Alabart]

Dear co-developpers,

I've been looking at improving build.xml to optimize the build process,
to allow for partial compilation, and to add developer targets.

In the process, I've discovered that a clean separation between the
different sections (jorphan,core,components,functions,protocol/*) has a
great advantage for developers: the dependency tree is quite simple,
which helps a lot in limiting the possible impact of changes:

- core only depends on jorphan
- all others depend only on core and jorphan.

Unfortunately, the separation is not as clean as it should be. To clean
it up, it is necessary to:
1/ Move some files from components into core -- this is OK, it's only for really "core" components.
2/ Remove the loading of legacy test plans.
3/ Change some unit tests.

I'm working towards solutions for 3/, but there's no clean solution for 2/.

The question is: how much do we still need being able to load legacy
test plans? Is this something we could remove now?

Salut,

Jordi.




--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>