Re: About the groovy code style

2018-07-03 Thread Daniel.Sun
Hi Paul, > def foobar2 = 'foo' > + 'bar2' > > which compiles but gives a runtime error: > MissingMethodException: No signature of method: > java.lang.String.positive() > > > Since + here is the unary plus operator which while seldom used in that > fashion is a valid operator. > > Strangely

Re: About the groovy code style

2018-07-03 Thread Daniel.Sun
ping Danil :-) - Daniel Sun Apache Groovy committer Blog: http://blog.sunlan.me Twitter: @daniel_sun -- Sent from: http://groovy.329449.n5.nabble.com/Groovy-Users-f329450.html

Re: New webapp development kit using Groovy

2018-07-03 Thread Simon Sadedin
Congrats on the release! Looks like a sort of full-stack version of Vert.x or similar (or micronaut for that matter). Actually would fit the bill for a lot of projects where I find grails too heavy and slow, especially for SPAs where the front end is very decoupled from the back end. Will be givi

Re: Groovy with OpenJDK 10 and IntelliJ Build

2018-07-03 Thread MG
No, you pick the JDK for the project/module independently from the IDE. One problem is that IntelliJ does not (afaikt - I never had the need to do so before) support passing parameters to the Groovy compiler (you can supply a Groovy configscript). On 04.07.2018 01:35, Paul King wrote: Does the

Re: Groovy with OpenJDK 10 and IntelliJ Build

2018-07-03 Thread Paul King
Does the JDK you run Intellij under need to be the same as what your project settings point to? On Wed, Jul 4, 2018 at 9:28 AM MG wrote: > Hi, > > does anyone allready have experience compiling a Groovy project under > IntelliJ and OpenJDK 10 ? > We are currently using OpenJDK 8 and would need t

Groovy with OpenJDK 10 and IntelliJ Build

2018-07-03 Thread MG
Hi, does anyone allready have experience compiling a Groovy project under IntelliJ and OpenJDK 10 ? We are currently using OpenJDK 8 and would need to evaluate (if possible) if our Groovy framework has any problems building & running under OpenJDK 10. We are using IntelliJ modules as our build

Re: New webapp development kit using Groovy

2018-07-03 Thread Edmond Kemokai
interesting, I'll dig into Kiss to see if there are any Gems I find useful...thanks for sharing. On Tue, Jul 3, 2018 at 12:23 PM, Blake McBride wrote: > Hi Edmond, > > I have done a number of web-based business applications over the years > (e.g. arahant.com, yumyum.io, booklion.com ) and throug

Re: New webapp development kit using Groovy

2018-07-03 Thread Blake McBride
Hi Edmond, I have done a number of web-based business applications over the years (e.g. arahant.com, yumyum.io, booklion.com ) and through it, a system began to emerge. Having written other development tools over the years (e.g. Dynace , APLUtils

Re: New webapp development kit using Groovy

2018-07-03 Thread Edmond Kemokai
Hi Blake, This is intriguing, what prompted you to create it? are you using it for any projects? At Codesolvent (codesolvent.com), our platform which uses Groovy in a somewhat related way via JSR-228, tackles similar problems. Is there any sort of UI IDE component to this? You mentioned " advanc

Re: About the groovy code style

2018-07-03 Thread Jochen Theodorou
Am 03.07.2018 um 04:44 schrieb Daniel.Sun: Hi all, The following code is supported in the older parser, but I propose to stop supporting the ugly code style in the new Parrot parser. Any thoughts? 1) import statement ( https://issues.apache.org/jira/browse/GROOVY-8642 ) ``` import java

New webapp development kit using Groovy

2018-07-03 Thread Blake McBride
Greetings, I put together an open-source web application development system that uses Groovy. It is a complete (front-end and back-end) solution for web-based business applications. It includes features such as microservices, SQL support, custom HTML tags, REST services, user authentication, etc

Re: Groovy 2.5.1 planning

2018-07-03 Thread Cédric Champeau
+1 Le mar. 3 juil. 2018 à 08:37, Paul King a écrit : > > Hi everyone, > > Even though I still have plenty of bugs on my "would like to fix before > next release" list, > I'd like to release a 2.5.1 fairly soon. This is mostly to do with 2.5.0 > inadvertently breaking > our OSGi support [1] but a