On Wednesday 04 March 2015 09:23:06 Martin Grigorov wrote: > On Wed, Mar 4, 2015 at 9:13 AM, Emond Papegaaij <emond.papega...@topicus.nl> > > > WicketStuff InMethodGrid is currently excluded from the build in 7.x > > > because it uses the old Tree and for 2 years no one spend his time to > > > fix > > > the deprecation warnings and migrate it to the new Tree impl... > > > > So are we going to re-introduce it now the code stays available? :) > > Yes. InMethod Grid is used by many applications. Most of its users probably > do not even know it uses deprecated APIs. > > One way is to leave it disabled and force the community to migrate it. > Another way is to copy the old Tree classes in InMethod Grid project and > use them locally. > The third way is to introduce a project for the old Tree, with deprecated > classes and documentation explaining that it is not maintained. >
I'd go for the third option then. Put all deprecated code in a separate project (or module), disable things like tests and code analysis, mark all classes as deprecated and leave them there to rot away. This keeps the work required to a minimum while still keeping the classes available for as long as possible. Best regards, Emond
