Deprecation is for 1.5.1 Extraction is for 2.0 Essentially anything that disappears in 2.0 may be deprecated (with or replacement) in the 1.5.x series simply for documentation purposes.
2.0 does NOT guarantee to be API compatible with 1.5.x. The JDK is a mess due to long-term deprecations. Heck some of the deprecated functions don't work anymore even. Lets keep it clean. -Andy Rainer Klute wrote: >>Also, removing org.apache.poi.hpsf.littleendian.* from HPSF is going to requir >> >e > >>breaking method signatures. org.apache.poi.hpsf.Section has methods like: >> >>public ClassID getFormatID() >> >>My preference is to deprecate. I already know Andy wants to slash and burn. >> > >I also prefer slash and burn. However, whether you deprecate them >or get rid of them: you need a replacement. Do you patches cover >this? > >Best regards >Rainer Klute > > Rainer Klute IT-Consulting GmbH i. Gr. > Dipl.-Inform. > Rainer Klute E-Mail: [EMAIL PROTECTED] > K�rner Grund 24 Telefon: +49 172 2324824 >D-44143 Dortmund Telefax: +49 231 5349423 > > >-- >To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> >For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
