[
https://issues.apache.org/jira/browse/TIKA-1536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14300768#comment-14300768
]
Nick Burch commented on TIKA-1536:
----------------------------------
I don't think it needs to wait for 2.0 - we moved from Java 5 to 6 within the
1.x series already
However, I think it might be best to do one more release on Java 6 which is
clearly flagged as the "last Java 6 release", then upgrade after that. That
would give any remaining Java 6 users time to speak up to make a case, would
give them notice, and would give a clear point to work from if there was
community interest in maintaining a Java 6 branch/series at a later date.
> Upgrade compiler definition in pom's to Java 7
> ----------------------------------------------
>
> Key: TIKA-1536
> URL: https://issues.apache.org/jira/browse/TIKA-1536
> Project: Tika
> Issue Type: Improvement
> Components: packaging
> Affects Versions: 1.7
> Reporter: Lewis John McGibbney
> Assignee: Lewis John McGibbney
> Fix For: 1.8
>
> Attachments: TIKA-1536.patch
>
>
> Since we committed TIKA-1423 it would appear through [mailing
> list|http://www.mail-archive.com/dev%40tika.apache.org/msg11542.html]
> commentary that there is a willingness to drop support for Java 1.6 in favour
> of >= Java 1.7.
> This issue simply addresses this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
