[jira] [Commented] (LUCENE-3239) drop java 5 support
[ https://issues.apache.org/jira/browse/LUCENE-3239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13057765#comment-13057765 ] Uwe Schindler commented on LUCENE-3239: --- Patch looks fine, Jenkins already moved. drop java 5 support - Key: LUCENE-3239 URL: https://issues.apache.org/jira/browse/LUCENE-3239 Project: Lucene - Java Issue Type: Task Reporter: Robert Muir Attachments: LUCENE-3239.patch its been discussed here and there, but I think we need to drop java 5 support, for these reasons: * its totally untested by any continual build process. Testing java5 only when there is a release candidate ready is not enough. If we are to claim support then we need a hudson actually running the tests with java 5. * its now unmaintained, so bugs have to either be hacked around, tests disabled, warnings placed, but some things simply cannot be fixed... we cannot actually support something that is no longer maintained: we do find JRE bugs (http://wiki.apache.org/lucene-java/SunJavaBugs) and its important that bugs actually get fixed: cannot do everything with hacks. * because of its limitations, we do things like allow 20% slower grouping speed. I find it hard to believe we are sacrificing performance for this. So, in summary: because we don't test it at all, because its buggy and unmaintained, and because we are sacrificing performance, I think we need to cutover the build system for the next release to require java 6. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-3239) drop java 5 support
[ https://issues.apache.org/jira/browse/LUCENE-3239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13057772#comment-13057772 ] Simon Willnauer commented on LUCENE-3239: - I just committed that patch, I will continue on all the *.java TODOs drop java 5 support - Key: LUCENE-3239 URL: https://issues.apache.org/jira/browse/LUCENE-3239 Project: Lucene - Java Issue Type: Task Reporter: Robert Muir Attachments: LUCENE-3239.patch its been discussed here and there, but I think we need to drop java 5 support, for these reasons: * its totally untested by any continual build process. Testing java5 only when there is a release candidate ready is not enough. If we are to claim support then we need a hudson actually running the tests with java 5. * its now unmaintained, so bugs have to either be hacked around, tests disabled, warnings placed, but some things simply cannot be fixed... we cannot actually support something that is no longer maintained: we do find JRE bugs (http://wiki.apache.org/lucene-java/SunJavaBugs) and its important that bugs actually get fixed: cannot do everything with hacks. * because of its limitations, we do things like allow 20% slower grouping speed. I find it hard to believe we are sacrificing performance for this. So, in summary: because we don't test it at all, because its buggy and unmaintained, and because we are sacrificing performance, I think we need to cutover the build system for the next release to require java 6. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-3239) drop java 5 support
[ https://issues.apache.org/jira/browse/LUCENE-3239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13057780#comment-13057780 ] Uwe Schindler commented on LUCENE-3239: --- +1 as a start drop java 5 support - Key: LUCENE-3239 URL: https://issues.apache.org/jira/browse/LUCENE-3239 Project: Lucene - Java Issue Type: Task Reporter: Robert Muir Attachments: LUCENE-3239.patch, LUCENE-3239.patch its been discussed here and there, but I think we need to drop java 5 support, for these reasons: * its totally untested by any continual build process. Testing java5 only when there is a release candidate ready is not enough. If we are to claim support then we need a hudson actually running the tests with java 5. * its now unmaintained, so bugs have to either be hacked around, tests disabled, warnings placed, but some things simply cannot be fixed... we cannot actually support something that is no longer maintained: we do find JRE bugs (http://wiki.apache.org/lucene-java/SunJavaBugs) and its important that bugs actually get fixed: cannot do everything with hacks. * because of its limitations, we do things like allow 20% slower grouping speed. I find it hard to believe we are sacrificing performance for this. So, in summary: because we don't test it at all, because its buggy and unmaintained, and because we are sacrificing performance, I think we need to cutover the build system for the next release to require java 6. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-3239) drop java 5 support
[ https://issues.apache.org/jira/browse/LUCENE-3239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13057781#comment-13057781 ] Simon Willnauer commented on LUCENE-3239: - bq. +1 as a start alright I'll kick it in... we are on 1.6 YAY! drop java 5 support - Key: LUCENE-3239 URL: https://issues.apache.org/jira/browse/LUCENE-3239 Project: Lucene - Java Issue Type: Task Reporter: Robert Muir Attachments: LUCENE-3239.patch, LUCENE-3239.patch its been discussed here and there, but I think we need to drop java 5 support, for these reasons: * its totally untested by any continual build process. Testing java5 only when there is a release candidate ready is not enough. If we are to claim support then we need a hudson actually running the tests with java 5. * its now unmaintained, so bugs have to either be hacked around, tests disabled, warnings placed, but some things simply cannot be fixed... we cannot actually support something that is no longer maintained: we do find JRE bugs (http://wiki.apache.org/lucene-java/SunJavaBugs) and its important that bugs actually get fixed: cannot do everything with hacks. * because of its limitations, we do things like allow 20% slower grouping speed. I find it hard to believe we are sacrificing performance for this. So, in summary: because we don't test it at all, because its buggy and unmaintained, and because we are sacrificing performance, I think we need to cutover the build system for the next release to require java 6. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-3239) drop java 5 support
[ https://issues.apache.org/jira/browse/LUCENE-3239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13054827#comment-13054827 ] Simon Willnauer commented on LUCENE-3239: - bq. So let me make sure we are on the same page: +1 drop java 5 support - Key: LUCENE-3239 URL: https://issues.apache.org/jira/browse/LUCENE-3239 Project: Lucene - Java Issue Type: Task Reporter: Robert Muir its been discussed here and there, but I think we need to drop java 5 support, for these reasons: * its totally untested by any continual build process. Testing java5 only when there is a release candidate ready is not enough. If we are to claim support then we need a hudson actually running the tests with java 5. * its now unmaintained, so bugs have to either be hacked around, tests disabled, warnings placed, but some things simply cannot be fixed... we cannot actually support something that is no longer maintained: we do find JRE bugs (http://wiki.apache.org/lucene-java/SunJavaBugs) and its important that bugs actually get fixed: cannot do everything with hacks. * because of its limitations, we do things like allow 20% slower grouping speed. I find it hard to believe we are sacrificing performance for this. So, in summary: because we don't test it at all, because its buggy and unmaintained, and because we are sacrificing performance, I think we need to cutover the build system for the next release to require java 6. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-3239) drop java 5 support
[ https://issues.apache.org/jira/browse/LUCENE-3239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13054896#comment-13054896 ] Dawid Weiss commented on LUCENE-3239: - +1 from me. drop java 5 support - Key: LUCENE-3239 URL: https://issues.apache.org/jira/browse/LUCENE-3239 Project: Lucene - Java Issue Type: Task Reporter: Robert Muir its been discussed here and there, but I think we need to drop java 5 support, for these reasons: * its totally untested by any continual build process. Testing java5 only when there is a release candidate ready is not enough. If we are to claim support then we need a hudson actually running the tests with java 5. * its now unmaintained, so bugs have to either be hacked around, tests disabled, warnings placed, but some things simply cannot be fixed... we cannot actually support something that is no longer maintained: we do find JRE bugs (http://wiki.apache.org/lucene-java/SunJavaBugs) and its important that bugs actually get fixed: cannot do everything with hacks. * because of its limitations, we do things like allow 20% slower grouping speed. I find it hard to believe we are sacrificing performance for this. So, in summary: because we don't test it at all, because its buggy and unmaintained, and because we are sacrificing performance, I think we need to cutover the build system for the next release to require java 6. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-3239) drop java 5 support
[ https://issues.apache.org/jira/browse/LUCENE-3239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13054525#comment-13054525 ] Uwe Schindler commented on LUCENE-3239: --- As said yesterday to you privately: I agree with making Lucene trunk Java 6 only - Surprise. But 3.x should stay with Java 5. Is this ok for you? I know, Simon will not agree because he made DocValues for Android *g* About Hudson testing: We may donate a machine to Infra just for Lucene tests running something nice like Ubuntu, stay tuned (no details, I just say that). drop java 5 support - Key: LUCENE-3239 URL: https://issues.apache.org/jira/browse/LUCENE-3239 Project: Lucene - Java Issue Type: Task Reporter: Robert Muir its been discussed here and there, but I think we need to drop java 5 support, for these reasons: * its totally untested by any continual build process. Testing java5 only when there is a release candidate ready is not enough. If we are to claim support then we need a hudson actually running the tests with java 5. * its now unmaintained, so bugs have to either be hacked around, tests disabled, warnings placed, but some things simply cannot be fixed... we cannot actually support something that is no longer maintained: we do find JRE bugs (http://wiki.apache.org/lucene-java/SunJavaBugs) and its important that bugs actually get fixed: cannot do everything with hacks. * because of its limitations, we do things like allow 20% slower grouping speed. I find it hard to believe we are sacrificing performance for this. So, in summary: because we don't test it at all, because its buggy and unmaintained, and because we are sacrificing performance, I think we need to cutover the build system for the next release to require java 6. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-3239) drop java 5 support
[ https://issues.apache.org/jira/browse/LUCENE-3239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13054542#comment-13054542 ] Robert Muir commented on LUCENE-3239: - bq. About Hudson testing: We may donate a machine to Infra just for Lucene tests running something nice like Ubuntu, stay tuned (no details, I just say that). And when this time comes, we could consider supporting java 5. But right now, we don't have a way to test it. drop java 5 support - Key: LUCENE-3239 URL: https://issues.apache.org/jira/browse/LUCENE-3239 Project: Lucene - Java Issue Type: Task Reporter: Robert Muir its been discussed here and there, but I think we need to drop java 5 support, for these reasons: * its totally untested by any continual build process. Testing java5 only when there is a release candidate ready is not enough. If we are to claim support then we need a hudson actually running the tests with java 5. * its now unmaintained, so bugs have to either be hacked around, tests disabled, warnings placed, but some things simply cannot be fixed... we cannot actually support something that is no longer maintained: we do find JRE bugs (http://wiki.apache.org/lucene-java/SunJavaBugs) and its important that bugs actually get fixed: cannot do everything with hacks. * because of its limitations, we do things like allow 20% slower grouping speed. I find it hard to believe we are sacrificing performance for this. So, in summary: because we don't test it at all, because its buggy and unmaintained, and because we are sacrificing performance, I think we need to cutover the build system for the next release to require java 6. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-3239) drop java 5 support
[ https://issues.apache.org/jira/browse/LUCENE-3239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13054629#comment-13054629 ] Mark Miller commented on LUCENE-3239: - That seems reasonable to me - officially we endorse/support java 6, but we can the 3.x line to 5 features. I can live with that myself. drop java 5 support - Key: LUCENE-3239 URL: https://issues.apache.org/jira/browse/LUCENE-3239 Project: Lucene - Java Issue Type: Task Reporter: Robert Muir its been discussed here and there, but I think we need to drop java 5 support, for these reasons: * its totally untested by any continual build process. Testing java5 only when there is a release candidate ready is not enough. If we are to claim support then we need a hudson actually running the tests with java 5. * its now unmaintained, so bugs have to either be hacked around, tests disabled, warnings placed, but some things simply cannot be fixed... we cannot actually support something that is no longer maintained: we do find JRE bugs (http://wiki.apache.org/lucene-java/SunJavaBugs) and its important that bugs actually get fixed: cannot do everything with hacks. * because of its limitations, we do things like allow 20% slower grouping speed. I find it hard to believe we are sacrificing performance for this. So, in summary: because we don't test it at all, because its buggy and unmaintained, and because we are sacrificing performance, I think we need to cutover the build system for the next release to require java 6. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-3239) drop java 5 support
[ https://issues.apache.org/jira/browse/LUCENE-3239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13054728#comment-13054728 ] Robert Muir commented on LUCENE-3239: - +1, this seems like a good compromise. So let me make sure we are on the same page: * trunk moves to java6 (all of the source tree, not just solr/) * branch_3x stays the same (limit ourselves to what compiles with java5), its already the de-facto reality that java5 is not officially supported since we do not even test it. drop java 5 support - Key: LUCENE-3239 URL: https://issues.apache.org/jira/browse/LUCENE-3239 Project: Lucene - Java Issue Type: Task Reporter: Robert Muir its been discussed here and there, but I think we need to drop java 5 support, for these reasons: * its totally untested by any continual build process. Testing java5 only when there is a release candidate ready is not enough. If we are to claim support then we need a hudson actually running the tests with java 5. * its now unmaintained, so bugs have to either be hacked around, tests disabled, warnings placed, but some things simply cannot be fixed... we cannot actually support something that is no longer maintained: we do find JRE bugs (http://wiki.apache.org/lucene-java/SunJavaBugs) and its important that bugs actually get fixed: cannot do everything with hacks. * because of its limitations, we do things like allow 20% slower grouping speed. I find it hard to believe we are sacrificing performance for this. So, in summary: because we don't test it at all, because its buggy and unmaintained, and because we are sacrificing performance, I think we need to cutover the build system for the next release to require java 6. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-3239) drop java 5 support
[ https://issues.apache.org/jira/browse/LUCENE-3239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13054735#comment-13054735 ] DM Smith commented on LUCENE-3239: -- Same page. drop java 5 support - Key: LUCENE-3239 URL: https://issues.apache.org/jira/browse/LUCENE-3239 Project: Lucene - Java Issue Type: Task Reporter: Robert Muir its been discussed here and there, but I think we need to drop java 5 support, for these reasons: * its totally untested by any continual build process. Testing java5 only when there is a release candidate ready is not enough. If we are to claim support then we need a hudson actually running the tests with java 5. * its now unmaintained, so bugs have to either be hacked around, tests disabled, warnings placed, but some things simply cannot be fixed... we cannot actually support something that is no longer maintained: we do find JRE bugs (http://wiki.apache.org/lucene-java/SunJavaBugs) and its important that bugs actually get fixed: cannot do everything with hacks. * because of its limitations, we do things like allow 20% slower grouping speed. I find it hard to believe we are sacrificing performance for this. So, in summary: because we don't test it at all, because its buggy and unmaintained, and because we are sacrificing performance, I think we need to cutover the build system for the next release to require java 6. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org