You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tika.apache.org by "Tyler Palsulich (JIRA)" <ji...@apache.org> on 2015/01/31 22:25:34 UTC

[jira] [Commented] (TIKA-1536) Upgrade compiler definition in pom's to Java 7

    [ https://issues.apache.org/jira/browse/TIKA-1536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14299992#comment-14299992 ] 

Tyler Palsulich commented on TIKA-1536:
---------------------------------------

Should we hold off on this until 2.0? Or, is it worth including in 1.8? I'm not sure which I'd prefer, but I think it's worth some discussion.

> 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)