[jira] [Comment Edited] (GROOVY-9968) @TypeChecked Error: Members of Iterable are Foo, not Object

[ https://issues.apache.org/jira/browse/GROOVY-9968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17296397#comment-17296397 ] mgroovy edited comment on GROOVY-9968 at 3/6/21, 12:20 AM: --- * Yes, exactly. *

[jira] [Commented] (GROOVY-9968) @TypeChecked Error: Members of Iterable are Foo, not Object

[ https://issues.apache.org/jira/browse/GROOVY-9968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17296397#comment-17296397 ] mgroovy commented on GROOVY-9968: - * Yes, exactly. * The error also occurs when saying e.g. (Note:

[jira] [Commented] (GROOVY-9968) @TypeChecked Error: Members of Iterable are Foo, not Object

[ https://issues.apache.org/jira/browse/GROOVY-9968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17296279#comment-17296279 ] mgroovy commented on GROOVY-9968: - Sorry, Eric, so trivial that I forgot to include... > @TypeChecked

[jira] [Updated] (GROOVY-9968) @TypeChecked Error: Members of Iterable are Foo, not Object

[ https://issues.apache.org/jira/browse/GROOVY-9968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] mgroovy updated GROOVY-9968: Description: *Problem* Trying to build the sample test code below fails with: {code:java} Groovyc:

[jira] [Updated] (GROOVY-9968) @TypeChecked Error: Members of Iterable are Foo, not Object

[ https://issues.apache.org/jira/browse/GROOVY-9968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] mgroovy updated GROOVY-9968: Description: *Problem* Trying to build the sample test code below fails with: {code:java} Groovyc:

[jira] [Updated] (GROOVY-9968) @TypeChecked Error: Members of Iterable are Foo, not Object

[ https://issues.apache.org/jira/browse/GROOVY-9968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] mgroovy updated GROOVY-9968: Description: *Problem* Trying to build the sample test code below fails with: {code:java} Groovyc:

[jira] [Updated] (GROOVY-9968) @TypeChecked Error: Members of Iterable are Foo, not Object

[ https://issues.apache.org/jira/browse/GROOVY-9968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] mgroovy updated GROOVY-9968: Description: *Problem* Trying to build the sample test code below fails with: {code:java} Groovyc:

[jira] [Updated] (GROOVY-9968) @TypeChecked Error: Members of Iterable are Foo, not Object

[ https://issues.apache.org/jira/browse/GROOVY-9968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] mgroovy updated GROOVY-9968: Description: *Problem* Trying to build the sample test code below fails with: {code:java} Groovyc:

[jira] [Created] (GROOVY-9968) @TypeChecked Error: Members of Iterable are Foo, not Object

mgroovy created GROOVY-9968: --- Summary: @TypeChecked Error: Members of Iterable are Foo, not Object Key: GROOVY-9968 URL: https://issues.apache.org/jira/browse/GROOVY-9968 Project: Groovy Issue

[jira] [Updated] (GROOVY-9966) Build Error: StringIndexOutOfBoundsException when the stars align...

[ https://issues.apache.org/jira/browse/GROOVY-9966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] mgroovy updated GROOVY-9966: Description: *Problem* Trying to build the sample test code below throws: {code:java} Groovyc: While

[jira] [Created] (GROOVY-9966) Build Error: StringIndexOutOfBoundsException when the stars align...

mgroovy created GROOVY-9966: --- Summary: Build Error: StringIndexOutOfBoundsException when the stars align... Key: GROOVY-9966 URL: https://issues.apache.org/jira/browse/GROOVY-9966 Project: Groovy

[jira] [Updated] (GROOVY-9965) Static generic method hiding instance method of same name leads to MME

[ https://issues.apache.org/jira/browse/GROOVY-9965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] mgroovy updated GROOVY-9965: Labels: generics static (was: generi static) > Static generic method hiding instance method of same name

[jira] [Updated] (GROOVY-9965) Static generic method hiding instance method of same name leads to MME

[ https://issues.apache.org/jira/browse/GROOVY-9965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] mgroovy updated GROOVY-9965: Summary: Static generic method hiding instance method of same name leads to MME (was: Static generic

[jira] [Updated] (GROOVY-9965) Static generic method hiding method of same name leads to MME

[ https://issues.apache.org/jira/browse/GROOVY-9965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] mgroovy updated GROOVY-9965: Description: *Problem* Executing the test from the sample below throws: {code:java}

[jira] [Updated] (GROOVY-9965) Static generic method hiding method of same name leads to MME

[ https://issues.apache.org/jira/browse/GROOVY-9965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] mgroovy updated GROOVY-9965: Description: *Problem* Executing the test from the sample below throws: {code:java}

[jira] [Created] (GROOVY-9965) Static generic method hiding method of same name leads to MME

mgroovy created GROOVY-9965: --- Summary: Static generic method hiding method of same name leads to MME Key: GROOVY-9965 URL: https://issues.apache.org/jira/browse/GROOVY-9965 Project: Groovy Issue

[jira] [Commented] (GROOVY-8258) [GEP] Create a LINQ-like DSL

[ https://issues.apache.org/jira/browse/GROOVY-8258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17208403#comment-17208403 ] mgroovy commented on GROOVY-8258: - @[~daniel_sun]: Hi Daniel * First congrats since it seems like you

[jira] [Commented] (GROOVY-9564) logo usage request

[ https://issues.apache.org/jira/browse/GROOVY-9564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17112563#comment-17112563 ] mgroovy commented on GROOVY-9564: - * Have you considered using the compact Groovy logo used here in the

[jira] [Commented] (GROOVY-9442) GEP: Support for the new JDK14 string escape sequence (\s for single space)

[ https://issues.apache.org/jira/browse/GROOVY-9442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17054505#comment-17054505 ] mgroovy commented on GROOVY-9442: - I still think \s sees more practical use than \b (so the argument "it

[jira] [Comment Edited] (GROOVY-9442) GEP: Support for the new JDK14 string escape sequence (\s for single space)

[ https://issues.apache.org/jira/browse/GROOVY-9442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17054218#comment-17054218 ] mgroovy edited comment on GROOVY-9442 at 3/7/20, 9:55 PM: -- "The only ve I can

[jira] [Comment Edited] (GROOVY-9442) GEP: Support for the new JDK14 string escape sequence (\s for single space)

[ https://issues.apache.org/jira/browse/GROOVY-9442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17054218#comment-17054218 ] mgroovy edited comment on GROOVY-9442 at 3/7/20, 9:55 PM: -- "The only ve I can

[jira] [Comment Edited] (GROOVY-9442) GEP: Support for the new JDK14 string escape sequence (\s for single space)

[ https://issues.apache.org/jira/browse/GROOVY-9442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17054218#comment-17054218 ] mgroovy edited comment on GROOVY-9442 at 3/7/20, 9:54 PM: -- "The only ve I can

[jira] [Comment Edited] (GROOVY-9442) GEP: Support for the new JDK14 string escape sequence (\s for single space)

[ https://issues.apache.org/jira/browse/GROOVY-9442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17054218#comment-17054218 ] mgroovy edited comment on GROOVY-9442 at 3/7/20, 9:54 PM: -- "The only ve I can

[jira] [Commented] (GROOVY-9442) GEP: Support for the new JDK14 string escape sequence (\s for single space)

[ https://issues.apache.org/jira/browse/GROOVY-9442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17054218#comment-17054218 ] mgroovy commented on GROOVY-9442: - "The only -ve I can see is regex users who might get regex \s mixed

[jira] [Comment Edited] (GROOVY-9442) GEP: Support for the new JDK14 string escape sequence (\s for single space)

[ https://issues.apache.org/jira/browse/GROOVY-9442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17054218#comment-17054218 ] mgroovy edited comment on GROOVY-9442 at 3/7/20, 9:53 PM: -- "The only ve I can

[jira] [Comment Edited] (GROOVY-9442) GEP: Support for the new JDK14 string escape sequence (\s for single space)

[ https://issues.apache.org/jira/browse/GROOVY-9442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17054138#comment-17054138 ] mgroovy edited comment on GROOVY-9442 at 3/7/20, 4:16 PM: -- Should imho not be

[jira] [Commented] (GROOVY-9442) GEP: Support for the new JDK14 string escape sequence (\s for single space)

[ https://issues.apache.org/jira/browse/GROOVY-9442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17054138#comment-17054138 ] mgroovy commented on GROOVY-9442: - Should imho not be supported for slashy strings: I see very little to

[jira] [Commented] (GROOVY-8580) CLONE - Support `var` keyword of Java10 (finalise behavior of keyword under @CompileStatic)

[ https://issues.apache.org/jira/browse/GROOVY-8580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17037282#comment-17037282 ] mgroovy commented on GROOVY-8580: - * If this has not yet been decided, I have one more (very practical)

[jira] [Commented] (GROOVY-8992) [GEP]Polish the generics type syntax for closure

[ https://issues.apache.org/jira/browse/GROOVY-8992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16770174#comment-16770174 ] mgroovy commented on GROOVY-8992: - * Alternative suggestion: {code}Closure{code} * This would put the

[jira] [Comment Edited] (GROOVY-8992) [GEP]Polish the generics type syntax for closure

[ https://issues.apache.org/jira/browse/GROOVY-8992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16770168#comment-16770168 ] mgroovy edited comment on GROOVY-8992 at 2/16/19 6:40 PM: -- * That's why I

[jira] [Comment Edited] (GROOVY-8992) [GEP]Polish the generics type syntax for closure

[ https://issues.apache.org/jira/browse/GROOVY-8992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16770168#comment-16770168 ] mgroovy edited comment on GROOVY-8992 at 2/16/19 6:46 PM: -- * That's why I

[jira] [Comment Edited] (GROOVY-8992) [GEP]Polish the generics type syntax for closure

[ https://issues.apache.org/jira/browse/GROOVY-8992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16770139#comment-16770139 ] mgroovy edited comment on GROOVY-8992 at 2/16/19 6:29 PM: -- * What about

[jira] [Comment Edited] (GROOVY-8992) [GEP]Polish the generics type syntax for closure

[ https://issues.apache.org/jira/browse/GROOVY-8992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16770168#comment-16770168 ] mgroovy edited comment on GROOVY-8992 at 2/16/19 6:36 PM: -- * That's why I

[jira] [Commented] (GROOVY-8992) [GEP]Polish the generics type syntax for closure

[ https://issues.apache.org/jira/browse/GROOVY-8992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16770168#comment-16770168 ] mgroovy commented on GROOVY-8992: - * That's why I suggested it: The result of the closure call is either

[jira] [Issue Comment Deleted] (GROOVY-8992) [GEP]Polish the generics type syntax for closure

[ https://issues.apache.org/jira/browse/GROOVY-8992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] mgroovy updated GROOVY-8992: Comment: was deleted (was: Will this also be supported: Closure<(Sql) : V> ? It seems a good idea for

[jira] [Commented] (GROOVY-8992) [GEP]Polish the generics type syntax for closure

[ https://issues.apache.org/jira/browse/GROOVY-8992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16770139#comment-16770139 ] mgroovy commented on GROOVY-8992: - * What about seperating the different argument varieties with |

[jira] [Commented] (GROOVY-8992) [GEP]Polish the generics type syntax for closure

[ https://issues.apache.org/jira/browse/GROOVY-8992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16770137#comment-16770137 ] mgroovy commented on GROOVY-8992: - Will this also be supported: Closure<(Sql) : V> ? It seems a good

[jira] [Updated] (GROOVY-8777) @MapConstructor: Creating inner class instance => IncompatibleClassChangeError ... does not implement the requested interface java.util.Map

[ https://issues.apache.org/jira/browse/GROOVY-8777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] mgroovy updated GROOVY-8777: Summary: @MapConstructor: Creating inner class instance => IncompatibleClassChangeError ... does not

[jira] [Created] (GROOVY-8777) @MapConstructor: Creating inner class instance => VerifyError: Bad type on operand stack CTE

mgroovy created GROOVY-8777: --- Summary: @MapConstructor: Creating inner class instance => VerifyError: Bad type on operand stack CTE Key: GROOVY-8777 URL: https://issues.apache.org/jira/browse/GROOVY-8777

[jira] [Updated] (GROOVY-8776) @MapConstructor: Creating static inner class instance => VerifyError: Bad type on operand stack CTE

[ https://issues.apache.org/jira/browse/GROOVY-8776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] mgroovy updated GROOVY-8776: Summary: @MapConstructor: Creating static inner class instance => VerifyError: Bad type on operand stack

[jira] [Created] (GROOVY-8776) @MapConstructor: Creating inner class instance => VerifyError: Bad type on operand stack CTE

mgroovy created GROOVY-8776: --- Summary: @MapConstructor: Creating inner class instance => VerifyError: Bad type on operand stack CTE Key: GROOVY-8776 URL: https://issues.apache.org/jira/browse/GROOVY-8776

[jira] [Comment Edited] (GROOVY-8580) CLONE - Support `var` keyword of Java10 (finalise behavior of keyword under @CompileStatic)

[ https://issues.apache.org/jira/browse/GROOVY-8580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16479850#comment-16479850 ] mgroovy edited comment on GROOVY-8580 at 5/17/18 11:36 PM: --- @[~daniel_sun]:

[jira] [Commented] (GROOVY-8580) CLONE - Support `var` keyword of Java10 (finalise behavior of keyword under @CompileStatic)

[ https://issues.apache.org/jira/browse/GROOVY-8580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16479850#comment-16479850 ] mgroovy commented on GROOVY-8580: - @[~daniel_sun]: Could you explain the difference between variant 2 and

[jira] [Commented] (GROOVY-8570) Support Warnings in Groovy Compiler

[ https://issues.apache.org/jira/browse/GROOVY-8570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16479845#comment-16479845 ] mgroovy commented on GROOVY-8570: - @[~blackdrag]: When would that converter run ? And who would implement

[jira] [Commented] (GROOVY-8570) Support Warnings in Groovy Compiler

[ https://issues.apache.org/jira/browse/GROOVY-8570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16479840#comment-16479840 ] mgroovy commented on GROOVY-8570: - @[~paulk]: You mean https://issues.apache.org/jira/browse/GROOVY-8580

[jira] [Commented] (GROOVY-8570) Support Warnings in Groovy Compiler

[ https://issues.apache.org/jira/browse/GROOVY-8570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16478097#comment-16478097 ] mgroovy commented on GROOVY-8570: - @[~paulk]: But how is someone to tell that "var" is bad style, and

[jira] [Commented] (GROOVY-8570) Support Warnings in Groovy Compiler

[ https://issues.apache.org/jira/browse/GROOVY-8570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16472033#comment-16472033 ] mgroovy commented on GROOVY-8570: - @[~paulk]: The question this boils down to for me is: Are you OK with

[jira] [Commented] (GROOVY-8570) Support Warnings in Groovy Compiler

[ https://issues.apache.org/jira/browse/GROOVY-8570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16470897#comment-16470897 ] mgroovy commented on GROOVY-8570: - And in general: Come on guys, it's only support for warnings, which

[jira] [Commented] (GROOVY-8570) Support Warnings in Groovy Compiler

[ https://issues.apache.org/jira/browse/GROOVY-8570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16470699#comment-16470699 ] mgroovy commented on GROOVY-8570: - (For any converter (formatter/transformer) which the user is not

[jira] [Commented] (GROOVY-8570) Support Warnings in Groovy Compiler

[ https://issues.apache.org/jira/browse/GROOVY-8570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16470681#comment-16470681 ] mgroovy commented on GROOVY-8570: - @[~blackdrag]: Do you mean a Java-to-Groovy converter, or a

[jira] [Commented] (GROOVY-8570) Support Warnings in Groovy Compiler

[ https://issues.apache.org/jira/browse/GROOVY-8570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16468101#comment-16468101 ] mgroovy commented on GROOVY-8570: - Let me advocate back: Curly braces and var should make your list of

[jira] [Commented] (GROOVY-8570) Support Warnings in Groovy Compiler

[ https://issues.apache.org/jira/browse/GROOVY-8570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16467875#comment-16467875 ] mgroovy commented on GROOVY-8570: - (shalt not type while riding the tram... - continued) ... that e.g. @

[jira] [Commented] (GROOVY-8570) Support Warnings in Groovy Compiler

[ https://issues.apache.org/jira/browse/GROOVY-8570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16467870#comment-16467870 ] mgroovy commented on GROOVY-8570: - @[~paulk]: Hi Paul, an opt-in codenarc hook might be useful, but it is

[jira] [Commented] (GROOVY-8570) Support Warnings in Groovy Compiler

[ https://issues.apache.org/jira/browse/GROOVY-8570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16465225#comment-16465225 ] mgroovy commented on GROOVY-8570: - @[~emilles]: The difference to the scenario you describe here is not

[jira] [Created] (GROOVY-8570) Support Warnings in Groovy Compiler

mgroovy created GROOVY-8570: --- Summary: Support Warnings in Groovy Compiler Key: GROOVY-8570 URL: https://issues.apache.org/jira/browse/GROOVY-8570 Project: Groovy Issue Type: New Feature

[jira] [Updated] (GROOVY-8566) Array initialization from list literal without "as" should be supported under static compilation

[ https://issues.apache.org/jira/browse/GROOVY-8566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] mgroovy updated GROOVY-8566: Issue Type: Improvement (was: Planned Work) > Array initialization from list literal without "as" should

[jira] [Updated] (GROOVY-8566) Array initialization from list literal without "as" should be supported under static compilation

[ https://issues.apache.org/jira/browse/GROOVY-8566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] mgroovy updated GROOVY-8566: Description: Dynamic Groovy supports initializing an array from a list literal: {code:java} @Test @Ignore

[jira] [Updated] (GROOVY-8566) Array initialization from list literal without "as" should be supported under static compilation

[ https://issues.apache.org/jira/browse/GROOVY-8566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] mgroovy updated GROOVY-8566: Summary: Array initialization from list literal without "as" should be supported under static compilation

[jira] [Created] (GROOVY-8566) Array initialization from list literal without "as" not supported under static compilation

mgroovy created GROOVY-8566: --- Summary: Array initialization from list literal without "as" not supported under static compilation Key: GROOVY-8566 URL: https://issues.apache.org/jira/browse/GROOVY-8566

[jira] [Updated] (GROOVY-8503) Fund Groovy Development

[ https://issues.apache.org/jira/browse/GROOVY-8503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] mgroovy updated GROOVY-8503: Description: Join the HMS Groovy Bounty, Pledge Allegiance and Pay your Groovy Pals ! This is an

[jira] [Commented] (GROOVY-8301) break/return/continue support in "Appended Block Closures"

[ https://issues.apache.org/jira/browse/GROOVY-8301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16424708#comment-16424708 ] mgroovy commented on GROOVY-8301: - @[~blackdrag]: Evidently you think of much broader, differently

[jira] [Commented] (GROOVY-8301) break/return/continue support in "Appended Block Closures"

[ https://issues.apache.org/jira/browse/GROOVY-8301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16424692#comment-16424692 ] mgroovy commented on GROOVY-8301: - Could the inlining be done much earlier ? I conceptually always see

[jira] [Commented] (GROOVY-8301) break/return/continue support in "Appended Block Closures"

[ https://issues.apache.org/jira/browse/GROOVY-8301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16410588#comment-16410588 ] mgroovy commented on GROOVY-8301: - Thank you for the input Paul. * Do you know why this was implemented

[jira] [Updated] (GROOVY-8503) Fund Groovy Development

[ https://issues.apache.org/jira/browse/GROOVY-8503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] mgroovy updated GROOVY-8503: Description: Join the HMS Groovy Bounty, Pledge Allegiance and Pay your Groovy Pals ! This is an

[jira] [Created] (GROOVY-8503) Fund Groovy Development

mgroovy created GROOVY-8503: --- Summary: Fund Groovy Development Key: GROOVY-8503 URL: https://issues.apache.org/jira/browse/GROOVY-8503 Project: Groovy Issue Type: Planned Work

[jira] [Commented] (GROOVY-8490) Extend @Newify to support a class name pattern parameter

[ https://issues.apache.org/jira/browse/GROOVY-8490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16386801#comment-16386801 ] mgroovy commented on GROOVY-8490: - * I would apply the pattern against the name the developer uses in his

[jira] [Updated] (GROOVY-8490) Extend @Newify to support a class name pattern parameter

[ https://issues.apache.org/jira/browse/GROOVY-8490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] mgroovy updated GROOVY-8490: Description: * @Newify should be extended to support a classNamePattern parameter * All class names inside

[jira] [Updated] (GROOVY-8490) Extend @Newify to support a class name pattern parameter

[ https://issues.apache.org/jira/browse/GROOVY-8490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] mgroovy updated GROOVY-8490: Description: * @Newify should be extended to support a classNamePattern parameter * All class names inside

[jira] [Comment Edited] (GROOVY-8490) Extend @Newify to support a class name pattern parameter

[ https://issues.apache.org/jira/browse/GROOVY-8490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385408#comment-16385408 ] mgroovy edited comment on GROOVY-8490 at 3/4/18 10:13 PM: -- Could be combined

[jira] [Comment Edited] (GROOVY-8490) Extend @Newify to support a class name pattern parameter

[ https://issues.apache.org/jira/browse/GROOVY-8490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385408#comment-16385408 ] mgroovy edited comment on GROOVY-8490 at 3/4/18 10:13 PM: -- Could be combined

[jira] [Commented] (GROOVY-8490) Extend @Newify to support a class name pattern parameter

[ https://issues.apache.org/jira/browse/GROOVY-8490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385408#comment-16385408 ] mgroovy commented on GROOVY-8490: - Could be combined with > Extend @Newify to support a class name

[jira] [Created] (GROOVY-8491) @NamingConvention: Supply class/method/field/... name patterns to compiler

mgroovy created GROOVY-8491: --- Summary: @NamingConvention: Supply class/method/field/... name patterns to compiler Key: GROOVY-8491 URL: https://issues.apache.org/jira/browse/GROOVY-8491 Project: Groovy

[jira] [Created] (GROOVY-8490) Extend @Newify to support a class name pattern parameter

mgroovy created GROOVY-8490: --- Summary: Extend @Newify to support a class name pattern parameter Key: GROOVY-8490 URL: https://issues.apache.org/jira/browse/GROOVY-8490 Project: Groovy Issue Type:

[jira] [Updated] (GROOVY-8451) Non-Map-Based Named Parameter Support

[ https://issues.apache.org/jira/browse/GROOVY-8451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] mgroovy updated GROOVY-8451: Description: * Groovy should support named parameters as available in many other languages:

[jira] [Commented] (GROOVY-8451) Non-Map-Based Named Parameter Support

[ https://issues.apache.org/jira/browse/GROOVY-8451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16331587#comment-16331587 ] mgroovy commented on GROOVY-8451: - * @[~paulk]: Backward compatibility will probably prohibit this again,

[jira] [Commented] (GROOVY-8451) Non-Map-Based Named Parameter Support

[ https://issues.apache.org/jira/browse/GROOVY-8451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16331508#comment-16331508 ] mgroovy commented on GROOVY-8451: - (An overview over parameter information in Java up to and including 8:

[jira] [Created] (GROOVY-8451) Non-Map-Based Named Parameter Support

mgroovy created GROOVY-8451: --- Summary: Non-Map-Based Named Parameter Support Key: GROOVY-8451 URL: https://issues.apache.org/jira/browse/GROOVY-8451 Project: Groovy Issue Type: Improvement

[jira] [Comment Edited] (GROOVY-8431) toDebugString method as a core concept

[ https://issues.apache.org/jira/browse/GROOVY-8431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16326623#comment-16326623 ] mgroovy edited comment on GROOVY-8431 at 1/15/18 11:25 PM: --- * @[~leonard84]: I

[jira] [Commented] (GROOVY-8431) toDebugString method as a core concept

[ https://issues.apache.org/jira/browse/GROOVY-8431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16312329#comment-16312329 ] mgroovy commented on GROOVY-8431: - Another question: Should a toDebugString property be supplied, so that

[jira] [Commented] (GROOVY-8431) toDebugString method as a core concept

[ https://issues.apache.org/jira/browse/GROOVY-8431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16312327#comment-16312327 ] mgroovy commented on GROOVY-8431: - GROOVY-3250 & GROOVY-4654 deal with cyclic dependencies. Since

[jira] [Commented] (GROOVY-8431) toDebugString method as a core concept

[ https://issues.apache.org/jira/browse/GROOVY-8431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16312310#comment-16312310 ] mgroovy commented on GROOVY-8431: - GROOVY-4302 is a similar feature as the Named Variable (NV) "macro" I

[jira] [Commented] (GROOVY-8431) toDebugString method as a core concept

[ https://issues.apache.org/jira/browse/GROOVY-8431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16312301#comment-16312301 ] mgroovy commented on GROOVY-8431: - GROOVY-4653 deals with inconsistency between "$foo" and foo.toString()

[jira] [Commented] (GROOVY-8431) toDebugString method as a core concept

[ https://issues.apache.org/jira/browse/GROOVY-8431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16312295#comment-16312295 ] mgroovy commented on GROOVY-8431: - * I am not sure that the existing InvokerHelper methods mentioned

[jira] [Commented] (GROOVY-8431) toDebugString method as a core concept

[ https://issues.apache.org/jira/browse/GROOVY-8431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16312284#comment-16312284 ] mgroovy commented on GROOVY-8431: - * @ "human readable output" - the goal is to have a: Concise textual

[jira] [Commented] (GROOVY-8431) toDebugString method as a core concept

[ https://issues.apache.org/jira/browse/GROOVY-8431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16312278#comment-16312278 ] mgroovy commented on GROOVY-8431: - * @ dump method: I would suggest leaving dump available as is, and

[jira] [Created] (GROOVY-8431) toDebugString method as a core concept

mgroovy created GROOVY-8431: --- Summary: toDebugString method as a core concept Key: GROOVY-8431 URL: https://issues.apache.org/jira/browse/GROOVY-8431 Project: Groovy Issue Type: Proposal

[jira] [Commented] (GROOVY-8385) CompileStatic: Improved method call/property access Java compatibility for Minecraft Forge obfuscation support

[ https://issues.apache.org/jira/browse/GROOVY-8385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16306872#comment-16306872 ] mgroovy commented on GROOVY-8385: - * When using groovy-all-2.4.14-SNAPSHOT.jar from Groovy JDK 8 Build

[jira] [Comment Edited] (GROOVY-8385) CompileStatic: Improved method call/property access Java compatibility for Minecraft Forge obfuscation support

[ https://issues.apache.org/jira/browse/GROOVY-8385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16302621#comment-16302621 ] mgroovy edited comment on GROOVY-8385 at 12/24/17 1:09 AM: --- I tried the fix in

[jira] [Commented] (GROOVY-8385) CompileStatic: Improved method call/property access Java compatibility for Minecraft Forge obfuscation support

[ https://issues.apache.org/jira/browse/GROOVY-8385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16302621#comment-16302621 ] mgroovy commented on GROOVY-8385: - I tried the fix in the current apache-groovy-sdk-2.4.14-SNAPSHOT.zip

[jira] [Commented] (GROOVY-8419) Groovyc: The variable ... is declared final but is reassigned

[ https://issues.apache.org/jira/browse/GROOVY-8419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16294417#comment-16294417 ] mgroovy commented on GROOVY-8419: - Very much looks like it. Issue seems to be of a general nature, not

[jira] [Updated] (GROOVY-8419) Groovyc: The variable ... is declared final but is reassigned

[ https://issues.apache.org/jira/browse/GROOVY-8419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] mgroovy updated GROOVY-8419: Description: Under Groovy apache-groovy-binary-2.5.0-beta-2 the following code {code} final Map

[jira] [Created] (GROOVY-8419) Groovyc: The variable ... is declared final but is reassigned

mgroovy created GROOVY-8419: --- Summary: Groovyc: The variable ... is declared final but is reassigned Key: GROOVY-8419 URL: https://issues.apache.org/jira/browse/GROOVY-8419 Project: Groovy Issue

[jira] [Created] (GROOVY-8418) getSet* property name => Cannot read write-only property exception

mgroovy created GROOVY-8418: --- Summary: getSet* property name => Cannot read write-only property exception Key: GROOVY-8418 URL: https://issues.apache.org/jira/browse/GROOVY-8418 Project: Groovy

[jira] [Commented] (GROOVY-8385) CompileStatic: Improved method call/property access Java compatibility for Minecraft Forge obfuscation support

[ https://issues.apache.org/jira/browse/GROOVY-8385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16285010#comment-16285010 ] mgroovy commented on GROOVY-8385: - The generated code for entity.@hurtResistantTime = 0 is: {code}

[jira] [Commented] (GROOVY-8385) CompileStatic: Improved method call/property access Java compatibility for Minecraft Forge obfuscation support

[ https://issues.apache.org/jira/browse/GROOVY-8385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16285008#comment-16285008 ] mgroovy commented on GROOVY-8385: - @[~blackdrag] (dev mailing list reply): Trying to access the field

[jira] [Commented] (GROOVY-8385) CompileStatic: Improved method call/property access Java compatibility for Minecraft Forge obfuscation support

[ https://issues.apache.org/jira/browse/GROOVY-8385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16284807#comment-16284807 ] mgroovy commented on GROOVY-8385: - @[~paulk]: Finally had some time to look at this again. Here is an

[jira] [Commented] (GROOVY-8397) ORA-01000: maximum open cursors exceeded

[ https://issues.apache.org/jira/browse/GROOVY-8397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16273808#comment-16273808 ] mgroovy commented on GROOVY-8397: - * Note: Setting enableMetaDataChecking = false would most likely work

[jira] [Comment Edited] (GROOVY-8397) ORA-01000: maximum open cursors exceeded

[ https://issues.apache.org/jira/browse/GROOVY-8397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16273344#comment-16273344 ] mgroovy edited comment on GROOVY-8397 at 12/1/17 1:24 AM: -- ...and it looks like

[jira] [Commented] (GROOVY-8397) ORA-01000: maximum open cursors exceeded

[ https://issues.apache.org/jira/browse/GROOVY-8397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16273344#comment-16273344 ] mgroovy commented on GROOVY-8397: - ...and it looks like it works :-) (full test suite will run during the

[jira] [Commented] (GROOVY-8397) ORA-01000: maximum open cursors exceeded

[ https://issues.apache.org/jira/browse/GROOVY-8397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16273277#comment-16273277 ] mgroovy commented on GROOVY-8397: - Quick response is truly appreciated. I got the 2_4_X binary artifact,

<    1   2   3   >