Scott Eade wrote: > Candidates for deprecation in 2.3.3: > > * ScheduleService - not going to be ported to Fulcrum, use Fulcrum > Quartz instead > * LocalizationService - use Fulcrum Localization instead - relevant > classes have not been carried over to trunk/2.4 so it should have > been deprecated already anyway > * IntakeService - same situation as l10n service > * MimeTypeService - ditto > * A bunch of other services for which we have Fulcrum components do > still actually exist in the trunk/2.4 - should we not deprecate > these also now so that we can have a cleaner base to work on with 2.4? I'd not deprecate any services in the 2.3 branch, I expressed my concerns about the state of their Fulcrum counterparts already. At least their inter-dependencies need to be resolved. Localization and Intake rely on the Factory and Pool services and the Parser component, which in turn depends on the Upload service. If you want to use one of them, you need to replace all. I would not want to recommend this to the user as long as we haven't sorted that mess out.
> What about removing some of the deprecated code before 2.3.3? It has > been ages since 2.3.2 was released so I think we can justify removing > this code. > > Candidates for removal before 2.3.3 include: > > * org.apache.turbine.util.SequencedHashtable > * org.apache.turbine.util.StringStackBuffer > * org.apache.turbine.util.FileUtils > * org.apache.turbine.util.BufferCache > * org.apache.turbine.util.QuickSort > * org.apache.turbine.util.Comparable > * org.apache.turbine.util.Log > * org.apache.java.lang.Bytes > * org.apache.java.security.MD5 > * org.apache.java.security.MessageDigest > * org.apache.turbine.util.db.UUIdGenerator > * org.apache.turbine.util.db.TableColumn > * org.apache.turbine.services.resources.TurbineResources > +1 on this one. Go ahead. Bye, Thomas. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
