Tyler, +1 to announce dropping java 6 support on next release (1.9) and do actual drop on next release after 1.9.
Just updating the announcement of 1.8 release doesn't warn people, who already updated to last Tika release, I think. Anyway, we can release in couple of months (at least with some deps updated and minor fixes that were made after 1.8-rc2). I saw in POI dev list that they are planning to cut another beta or release soon. What downstream project could we notify? Solr 5.1 requires java 7, as I know, so I wouldn't be affected. -- Best regards, Konstantin Gribov вт, 28 апр. 2015 г. в 1:43, Tyler Palsulich <[email protected]>: > I should have included the fact this is the last release planned to support > Java 1.6 in the announcement (as we talked about a while back). But, since > that has passed, should we just update the announcement on the website, > wait another release, or just drop Java 1.6 support when we release 1.9? > > I could be persuaded to do any of the above. > > Tyler > > On Mon, Apr 27, 2015 at 1:30 PM, Konstantin Gribov <[email protected]> > wrote: > > > As I remember, we thought about announcing some release last java 6 > > compatible one and give Tika users some time to migrate. E. g., we can > > announce 1.10 last java 6 release when releasing 1.9. IMHO, in such case > it > > wouldn't be a sudden change for downstream project developers and Tika > > users. > > > > -- > > Best regards, > > Konstantin Gribov > > > > пн, 27 апр. 2015 г. в 20:09, Allison, Timothy B. <[email protected]>: > > > > > Hi All, > > > > > > I can't remember where we are on this. Are we dropping support for > > Java > > > 1.6 in Tika 1.9? If so, should we open an issue to integrate > tika-java7 > > > into core, add diamond operators, catching multiple exceptions... > > anything > > > else...? > > > > > > Or, do we want to wait for Tika 2.0 or Tika 1.10? > > > > > > Best, > > > > > > Tim > > > > > > > > >
