From: Andrea A. <aa...@op...> - 2007-02-19 14:10:21
|
Simone ha scritto: > Ciao Andrea, > I think I talked a bit about the issue you are bringing up before and > meanwhile doing this work. > This change MUST be done in an incompatible way if we want to have main > NOT depending on coverage. > Moreover, unless we want to create a circular dependecy there is no way > to use the usual deprecation cycle, because > if we do so, main would depend on coverage which would depend on main. I disagree. Keeping the same packages as before while moving the classes from one module to the other would not have changed the API. That is: * move the classes, don't change package * create the new classes in the new packages * have the old ones extend the new ones and become empty shells to ensure API continuity * deprecate the old ones * on 2.5 or lated, remove the deprecated old ones. Cheers Andrea |