tika-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris A. Mattmann (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TIKA-1536) Upgrade compiler definition in pom's to Java 7
Date Sat, 07 Feb 2015 02:21:34 GMT

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

Chris A. Mattmann commented on TIKA-1536:

I agree with Nick. However this is so trivial to support, what we can do is the following
(and what I'd prefer). Let's roll a 1.7.1 which is the last Java6 release (branched from current
trunk). In that branch, we'll set the compiler flag to 1.6. Then, in trunk going forward,
(after the 1.7.1 release), we roll the next release (1.8) with support for Java7 going forward.
Would that work? I think it that we would have to roll back Lewis's updates in the 1.7.1 branch
to support GribParser then, am I correct? Or just state that GribParser doesn't work in 1.7.1?

> 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
> This issue simply addresses this.

This message was sent by Atlassian JIRA

View raw message