[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=14613631#comment-14613631 ] Hudson commented on TIKA-1536: -- SUCCESS: Integrated in tika-trunk-jdk1.7 #779 (See [https://builds.apache.org/job/tika-trunk-jdk1.7/779/]) TIKA-1536. Update CHANGES.txt with upgrade to Java 7. (tpalsulich: http://svn.apache.org/viewvc/tika/trunk/?view=rev&rev=1688780) * /tika/trunk/CHANGES.txt TIKA-1536. Upgrade to Java 1.7. (tpalsulich: http://svn.apache.org/viewvc/tika/trunk/?view=rev&rev=1688779) * /tika/trunk/pom.xml * /tika/trunk/tika-parent/pom.xml > 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.10 > > 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)
[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=14609536#comment-14609536 ] Lewis John McGibbney commented on TIKA-1536: +1 to upgrade. Nice one Tyler. > 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.10 > > 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)
[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=14605772#comment-14605772 ] Tyler Palsulich commented on TIKA-1536: --- Yep, see http://apache.markmail.org/thread/7oubuh4hp6rdlbch. > 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.10 > > 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)
[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=14605344#comment-14605344 ] Konstantin Gribov commented on TIKA-1536: - Did we announced that current release will be last supports java 1.6 somewhere? > 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.10 > > 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)
[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=14605300#comment-14605300 ] Tyler Palsulich commented on TIKA-1536: --- Now that 1.9 is released, are there any blockers for upgrading to Java 1.7? > 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.10 > > 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)
[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=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 1.7. > This issue simply addresses this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[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=14304388#comment-14304388 ] Tyler Palsulich commented on TIKA-1536: --- Are there significant upgrades we're looking to include in 1.8 for users who would not be able to upgrade to Java 7? If not, what is the difference between releasing 1.8 with no Java 6 support and releasing 1.8 with the announcement that 1.9 will not support Java 6? > 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)
[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=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)
[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=1422#comment-1422 ] 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)
