In the Modeling Project, when we've had to move, rename or deprecate stuff, we've moved entire plugins or features from o.e.foo/plugins/o.e.foo.old.plugin to o.e.foo/deprecated/o.e.foo.old.plugin (or o.e.foo/features/o.e.foo-feature to o.e.foo/deprecated/o.e.foo-feature).
That way it's stil there, but out of the way of the build processes, and clearly labelled as deprecated so that people browsing CVS sources will avoid it. After a year or two, that code can then, with PMC approval, be moved into a tar.gz on archive.eclipse.org where it can live out its days watching Matlock re-runs and complaining about "kids today." :) IMHO, code should never just be deleted, even if it's "internal." But then, IANAL, just paranoid of the Wrath of the IP Team. :) Nick 2008/6/25 Seva Lapsha <[EMAIL PROTECTED]>: > I've just discovered almost all the classes from > org.eclipse.php.internal.core.phpModel package have been suddenly removed > from CVS, which caused basic stuff inside org.eclipse.php.ui not to compile. > > IMHO there should be no reason to delete files from version control just > because somebody "started working on the API change", especially when there > are other files which depend on them. It should be done in the end of the > process, shouldn't it? > > Seva > > 2008/6/25 Roy Ganor <[EMAIL PROTECTED]>: >> >> Consulting with other committers, it is important to have a discussion >> about the new API. >> >> Two sessions will be held (scheduled later) about the API change, the >> first one to collect feedbacks and the second to present the final API. >> >> >> >> ________________________________ >> >> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On >> Behalf Of Roy Ganor >> Sent: Wednesday, June 25, 2008 1:24 PM >> To: PDT Developers >> Subject: [pdt-dev] PDT 1.1. - API updates following infra changes >> >> >> >> Hello there, >> >> >> >> Unavoidable step following our infra changes is to change Eclipse PDT 1.1 >> API. >> >> Yes, it is a necessary step rather than a desirable one, we first thought >> that we could write adapters to the old model but the ROI is low. In order >> to step forward we must "slice" the cake and make a few changes. A detailed >> document about our new API should be delivered shortly after we finish the >> migration work. >> >> >> >> The following extension points will be replaced with our new API: >> >> org.eclipse.php.core. includePathVariables >> org.eclipse.php.core.modelFilter >> org.eclipse.php.core.phpBuilderExtensions >> org.eclipse.php.core.phpModelExtensions >> org.eclipse.php.core.workspaceModelListener >> >> >> >> Regards, >> >> _______________________ >> Roy Ganor >> Team Leader, R&D >> tel. +972-3-7539637 >> mob. +972-52-3290-754 >> Zend Technologies Ltd. >> >> >> >> >> >> _______________________________________________ >> pdt-dev mailing list >> [email protected] >> https://dev.eclipse.org/mailman/listinfo/pdt-dev >> > > > _______________________________________________ > pdt-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/pdt-dev > > _______________________________________________ pdt-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/pdt-dev
