[
https://issues.apache.org/jira/browse/TIKA-1535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14514946#comment-14514946
]
ASF GitHub Bot commented on TIKA-1535:
--
GitHub user LukeLiush opened a pull request:
GitHub user LukeLiush opened a pull request:
https://github.com/apache/tika/pull/45
https://issues.apache.org/jira/browse/TIKA-1535 Inheritance modification...
... for the class MIMETypes
You can merge this pull request into a Git repository by running:
$ git pull
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
[
https://issues.apache.org/jira/browse/TIKA-241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14514384#comment-14514384
]
gil cattaneo commented on TIKA-241:
---
Sorry for the noise i found this bug only today
which
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?
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.
--
[
https://issues.apache.org/jira/browse/TIKA-241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14514496#comment-14514496
]
Ken Krugler commented on TIKA-241:
--
Hi Gil,
Sorry, not sure what you mean by as BR/R.
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
