Re: [VOTE] Apache Groovy Roadmap

2017-02-02 Thread Paul King
This thread has kind of gone into debate mode but I guess for the record I would be -1 on any releases having parrot that weren't marked as "experimental" or "incubating" until we thrash out future plans for dealing with Java 8 features (default methods on interfaces/"real" lambda expressions). I d

Re: [VOTE] Apache Groovy Roadmap

2017-02-02 Thread Jesper Steen Møller
Hi list > On 2 Feb 2017, at 11.58, Paul King wrote: > > This thread has kind of gone into debate mode but I guess for the > record I would be -1 on any releases having parrot that weren't marked > as "experimental" or "incubating" until we thrash out future plans for > dealing with Java 8 featur

Re: [VOTE] Apache Groovy Roadmap

2017-02-02 Thread Graeme Rocher
I'm in agreement that we should not commit to behaviour that we believe to be wrong and later break it (i.e. lambda's) So if we agree on a version that should be "the Parrot release" whether that is 2.6 or 3.0 we have to scope into that work resolving the semantics discussion. Cheers On Thu, Feb

Re: [VOTE] Apache Groovy Roadmap

2017-02-02 Thread Daniel Sun
As to the new features of Java 8, Parrot provides the same syntax but the backend is based on the existing groovy runtime. The approach can make some differences between Groovy and Java 8. Whether these differences are allowed or not depends on GLS. Like the inner class behaves a bit differ

Re: [VOTE] Apache Groovy Roadmap

2017-02-02 Thread Jochen Theodorou
I would like to have a clarification on 2 things before we really make a new version: * is changing to java7 as default a breaking change and requires a new major version? (that implies 3.0 soon and 4.0 for java8 not long after) * is it acceptable to have optional java8 only components (for exa

Re: [VOTE] Apache Groovy Roadmap

2017-02-02 Thread Keith Suderman
> On Feb 2, 2017, at 6:47 AM, Jesper Steen Møller wrote: > > 3. Major numbers should only be used if we mean to break stuff. Parrot > shouldn't. > On Feb 2, 2017, at 10:03 AM, Jochen Theodorou wrote: > > I would like to have a clarification on 2 things before we really make a new > version

I need I help to create two litlle scripts using groovy

2017-02-02 Thread pppablo
I am new to groovy and looking for help for the following: I have to develop two groovy scripts that should: 1) Access an database and return the last value and show on CUSTOMFIELD (JIRA SYSTEM) 2) When the user closed the subtask, I need to store this value (LOGWORK) in my table to calculate a

Fwd: I need I help to create two litlle scripts using groovy

2017-02-02 Thread Paul King
I have forwarded your question to the users list which is specifically designed for usage questions about Groovy. This list is for discussions about developing the Groovy language itself. Cheers, Paul. -- Forwarded message -- From: pppablo Date: Fri, Feb 3, 2017 at 4:15 AM Subje