[jira] [Commented] (GROOVY-7722) StackOverflowError when use anonymous class with generics.

[ https://issues.apache.org/jira/browse/GROOVY-7722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15354644#comment-15354644 ] Graeme Rocher commented on GROOVY-7722: --- Duplicated by https://issues.apache.org/ji

[jira] [Updated] (GROOVY-7864) Stack overflow correcting generics when using @CompileStatic

[ https://issues.apache.org/jira/browse/GROOVY-7864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graeme Rocher updated GROOVY-7864: -- Labels: duplicate (was: ) > Stack overflow correcting generics when using @CompileStatic > ---

[jira] [Commented] (GROOVY-7864) Stack overflow correcting generics when using @CompileStatic

[ https://issues.apache.org/jira/browse/GROOVY-7864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15354642#comment-15354642 ] Graeme Rocher commented on GROOVY-7864: --- This is a duplicate of https://issues.apac

[jira] [Commented] (GROOVY-2972) groovy.lang.ObjectRange.size() disobeys its contract for large ranges of Long values.

[ https://issues.apache.org/jira/browse/GROOVY-2972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15354625#comment-15354625 ] Thibault Kruse commented on GROOVY-2972: sorry, Paul fixed the size message alrea

[jira] [Commented] (GROOVY-2972) groovy.lang.ObjectRange.size() disobeys its contract for large ranges of Long values.

[ https://issues.apache.org/jira/browse/GROOVY-2972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15354615#comment-15354615 ] Thibault Kruse commented on GROOVY-2972: IntRange still has issues. The construct

[jira] [Updated] (GROOVY-7877) Range step method could work with Number not just int

[ https://issues.apache.org/jira/browse/GROOVY-7877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul King updated GROOVY-7877: -- Issue Type: Improvement (was: Bug) > Range step method could work with Number not just int > -

[jira] [Created] (GROOVY-7877) Range step method could work with Number not just int

Paul King created GROOVY-7877: - Summary: Range step method could work with Number not just int Key: GROOVY-7877 URL: https://issues.apache.org/jira/browse/GROOVY-7877 Project: Groovy Issue Type:

[jira] [Commented] (GROOVY-2972) groovy.lang.ObjectRange.size() disobeys its contract for large ranges of Long values.

[ https://issues.apache.org/jira/browse/GROOVY-2972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15354472#comment-15354472 ] Paul King commented on GROOVY-2972: --- Fixed as part of PR #143 > groovy.lang.ObjectRang

[jira] [Resolved] (GROOVY-2972) groovy.lang.ObjectRange.size() disobeys its contract for large ranges of Long values.

[ https://issues.apache.org/jira/browse/GROOVY-2972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul King resolved GROOVY-2972. --- Resolution: Fixed Fix Version/s: 2.5.0-beta-1 > groovy.lang.ObjectRange.size() disobeys its co

[jira] [Assigned] (GROOVY-2972) groovy.lang.ObjectRange.size() disobeys its contract for large ranges of Long values.

[ https://issues.apache.org/jira/browse/GROOVY-2972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul King reassigned GROOVY-2972: - Assignee: Paul King > groovy.lang.ObjectRange.size() disobeys its contract for large ranges of L

[jira] [Resolved] (GROOVY-5426) ObjectRange.iterator() is reliant on size()

[ https://issues.apache.org/jira/browse/GROOVY-5426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul King resolved GROOVY-5426. --- Resolution: Fixed Assignee: Paul King Fix Version/s: 2.5.0-beta-1 Fixed as part of PR

[jira] [Commented] (GROOVY-5426) ObjectRange.iterator() is reliant on size()

[ https://issues.apache.org/jira/browse/GROOVY-5426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15354468#comment-15354468 ] Paul King commented on GROOVY-5426: --- PR#143 proposed a reasonably elegant solution to t

[jira] [Commented] (GROOVY-7842) MarkupTemplateEngine Totally Broken

[ https://issues.apache.org/jira/browse/GROOVY-7842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15354010#comment-15354010 ] ASF GitHub Bot commented on GROOVY-7842: GitHub user jwagenleitner opened a pull

[GitHub] groovy pull request #358: GROOVY-7842 - MarkupTemplateEngine Totally Broken

GitHub user jwagenleitner opened a pull request: https://github.com/apache/groovy/pull/358 GROOVY-7842 - MarkupTemplateEngine Totally Broken When running under a Security Manager an exception would be thrown because the empty codebase value was added as a Permission name which ca

[jira] [Resolved] (GROOVY-7150) Redirection of output in javax.script.ScriptEngine.invokeFunction() doesn't work

[ https://issues.apache.org/jira/browse/GROOVY-7150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Wagenleitner resolved GROOVY-7150. --- Resolution: Fixed Assignee: John Wagenleitner Fix Version/s: 2.4.8 Th

[jira] [Commented] (GROOVY-7150) Redirection of output in javax.script.ScriptEngine.invokeFunction() doesn't work

[ https://issues.apache.org/jira/browse/GROOVY-7150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15353960#comment-15353960 ] ASF GitHub Bot commented on GROOVY-7150: Github user asfgit closed the pull reque

[GitHub] groovy pull request #230: GROOVY-7150 - Redirection of output in javax.scrip...

Github user asfgit closed the pull request at: https://github.com/apache/groovy/pull/230 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enab

[GitHub] groovy pull request #120: Changed the Range's step to Number instead of int

Github user paplorinc closed the pull request at: https://github.com/apache/groovy/pull/120 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is e

[jira] [Updated] (GROOVY-7876) ClassCastException when calling DefaultTypeTransformation#compareEqual

[ https://issues.apache.org/jira/browse/GROOVY-7876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew White updated GROOVY-7876: - Description: It appears that comparing two objects that both implement comparable with DefaultTy

[jira] [Commented] (GROOVY-7874) When serializing a document with xmlUtil, namespaces that are actually necessary, are being dropped as "unused"

[ https://issues.apache.org/jira/browse/GROOVY-7874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15352681#comment-15352681 ] Paul King commented on GROOVY-7874: --- Groovy's stance on this issue has been that once t

[jira] [Resolved] (GROOVY-7629) ObjectRange methods duplicate functionality and should not rely on size()

[ https://issues.apache.org/jira/browse/GROOVY-7629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul King resolved GROOVY-7629. --- Resolution: Fixed Fix Version/s: 2.5.0-beta-1 PR partially merged as per comments in the PR. T

[jira] [Assigned] (GROOVY-7629) ObjectRange methods duplicate functionality and should not rely on size()

[ https://issues.apache.org/jira/browse/GROOVY-7629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul King reassigned GROOVY-7629: - Assignee: Paul King > ObjectRange methods duplicate functionality and should not rely on size()

[jira] [Commented] (GROOVY-7629) ObjectRange methods duplicate functionality and should not rely on size()

[ https://issues.apache.org/jira/browse/GROOVY-7629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15352660#comment-15352660 ] ASF GitHub Bot commented on GROOVY-7629: Github user asfgit closed the pull reque

[GitHub] groovy pull request #143: GROOVY-7629 ObjectRange duplicate functionality an...

Github user asfgit closed the pull request at: https://github.com/apache/groovy/pull/143 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enab

[GitHub] groovy pull request #:

Github user paulk-asert commented on the pull request: https://github.com/apache/groovy/commit/f646e6e12abc3d1a9db0dcff74ff22ecadd986ca#commitcomment-18037282 In gradle/wrapper/gradle-wrapper.properties: In gradle/wrapper/gradle-wrapper.properties on line 6: We should disable t

[jira] [Resolved] (GROOVY-7585) ObjectRange strange semantics for mismatched arguments

[ https://issues.apache.org/jira/browse/GROOVY-7585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul King resolved GROOVY-7585. --- Resolution: Fixed Fix Version/s: 2.5.0-beta-1 Latest PR merged. In summary: numerous inconsist

[jira] [Assigned] (GROOVY-7585) ObjectRange strange semantics for mismatched arguments

[ https://issues.apache.org/jira/browse/GROOVY-7585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul King reassigned GROOVY-7585: - Assignee: Paul King > ObjectRange strange semantics for mismatched arguments > -

[GitHub] groovy pull request #142: Groovy-7585 improve behavior of ObjectRange

Github user asfgit closed the pull request at: https://github.com/apache/groovy/pull/142 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enab