Re: 2.4.9 release

2017-02-24 Thread Daniel Sun
Hi Paul, GROOVY-8085(https://issues.apache.org/jira/browse/GROOVY-8085) is critical enough to be fixed in 2.4.9. Cheers, Daniel.Sun -- View this message in context: http://groovy.329449.n5.nabble.com/2-4-9-release-tp5738711p5738729.html Sent from the Groovy Dev mailing list archive at N

Re: About a new annotation Groovydoc

2017-02-24 Thread Daniel Sun
Hi Guillaume, > what about a special GroovyDoc annotation? The original purpose to add Groovydoc annotation is to store groovydoc at runtime and get groovydoc easily by accessing the annotation as usual. If it is GroovyDoc annotation, how can we store groovydoc and get it at runt

Re: About a new annotation Groovydoc

2017-02-24 Thread Daniel Sun
If groovydoc exists and is related to the target element, @Groovydoc will be attached to the target element(i.e. Not all target elements). Cheers, Daniel.Sun -- View this message in context: http://groovy.329449.n5.nabble.com/About-a-new-annotation-Groovydoc-tp5738721p5738733.html Sent from th

Re: Help with pitching Groovy and Grails

2017-02-24 Thread Daniel Sun
Gotcha. Thank you, Jochen :) Cheers, Daniel.Sun -- View this message in context: http://groovy.329449.n5.nabble.com/Help-with-pitching-Groovy-and-Grails-tp5738679p5738734.html Sent from the Groovy Dev mailing list archive at Nabble.com.

Re: Help with pitching Groovy and Grails

2017-02-24 Thread Remi Forax
- Mail original - > De: "Jochen Theodorou" > À: dev@groovy.apache.org > Envoyé: Mercredi 22 Février 2017 22:49:01 > Objet: Re: Help with pitching Groovy and Grails > On 21.02.2017 22:51, Raviteja Lokineni wrote: >> Hi Devs, >> >> I was trying to pitch using Grails for one of our projects

Re: About a new annotation Groovydoc

2017-02-24 Thread Remi Forax
Technically, Python was not the first language to introduce the idea of using a plain string at the start of a function as documentation, all LISPs do that :) Rémi - Mail original - > De: "Daniel Sun" > À: d...@groovy.incubator.apache.org > Envoyé: Vendredi 24 Février 2017 03:46:53 > Ob

Re: Help with pitching Groovy and Grails

2017-02-24 Thread Jochen Theodorou
On 24.02.2017 10:04, Remi Forax wrote: - Mail original - De: "Jochen Theodorou" À: dev@groovy.apache.org Envoyé: Mercredi 22 Février 2017 22:49:01 Objet: Re: Help with pitching Groovy and Grails On 21.02.2017 22:51, Raviteja Lokineni wrote: [...] well, of course I should also me

Re: 2.4.9 release

2017-02-24 Thread Paul King
Hi Daniel, I believe we have had that issue for a while, so I think it can wait until 2.4.10 which we can certainly release very soon if we need to. There are a number of bugs which I am hoping to work on over the next couple of weeks, so we'll hopefully have plenty of justification in another rel

[VOTE] Release Groovy 2.4.9

2017-02-24 Thread Paul King
Dear community, I am happy to start the VOTE thread for a Groovy 2.4.9 release! This release includes 12 bug fixes/improvements as outlined in the changelog: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123&version=12339147 Tag: https://git1-us-west.apache.org/repos/asf

Re: [VOTE] Release Groovy 2.4.9

2017-02-24 Thread Guillaume Laforge
I had a couple test failures in the JSON module: :groovy-json:test json.StreamingJsonBuilderTest > testStreamingJsonBuilder FAILED org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during conversion: Error grabbing Grapes -- [download failed:

Re: 2.4.9 release

2017-02-24 Thread Daniel Sun
Hi Paul, I've fixed it: https://github.com/apache/groovy/pull/504 Cheers, Daniel.Sun -- View this message in context: http://groovy.329449.n5.nabble.com/2-4-9-release-tp5738711p5738746.html Sent from the Groovy Dev mailing list archive at Nabble.com.

Re: [VOTE] Release Groovy 2.4.9

2017-02-24 Thread Daniel Sun
Hi Paul, If the PR(https://github.com/apache/groovy/pull/504) for fixing GROOVY-8085 is merged, +1 from me. Cheers, Daniel.Sun -- View this message in context: http://groovy.329449.n5.nabble.com/VOTE-Release-Groovy-2-4-9-tp5738742p5738747.html Sent from the Groovy Dev mailing list archi

CompileStatic and CompileDynamic question

2017-02-24 Thread Raviteja Lokineni
I see this error during compile I am not able to figure out what's wrong with this. Is this a bug: [Static type checking] - Cannot call #(some.package.CustomClass1, java.util.Map , java.util.List ) with arguments [some.package.CustomClass1, java.util.Map , java.util.List ] The class is annotated

Re: CompileStatic and CompileDynamic question

2017-02-24 Thread Raviteja Lokineni
Figured it out never mind, it was a stupid of me. Had to look closely at the declared generics. On Fri, Feb 24, 2017 at 11:25 AM, Raviteja Lokineni < raviteja.lokin...@gmail.com> wrote: > I see this error during compile I am not able to figure out what's wrong > with this. Is this a bug: > > [Sta

Indy jars does not pull indy dependencies

2017-02-24 Thread Raviteja Lokineni
I was using groovy-templates:indy in my projects but the dependency tree was showing non-indy dependencies. So I had to do this: compile 'org.codehaus.groovy:groovy:2.4.7:indy' compile ('org.codehaus.groovy:groovy-templates:2.4.7:indy') { exclude module: 'groovy' exclude module: 'groovy-xm

[ANN] Grengine 1.1.1

2017-02-24 Thread Alain Stalder
Grengine is an engine for running and embedding Groovy in a Java VM. Release Notes 1.1.1: * New: Convenience loadClass() and loadMainClass() methods in BaseGrengine for using the default loader. * Deprecated: Instead of SourceUtil#getTextStartNoLinebreaks(), use the new method getTextStartN