Re: [VOTE] Release Apache Groovy 2.4.7

+1 (binding) built from src checked RAT validated checksums On Mon, Jun 6, 2016 at 3:11 PM, John Wagenleitner wrote: > +1 > > On Jun 3, 2016 10:20 AM, "Cédric Champeau" wrote: >> >> Dear community, >> >> I am happy to start the VOTE thread

Re: Add a marker interface to bypass Collections and Maps formatting

I am +1 on improving how we handle formatting for lists and maps. My default position would be -1 on an implementation that smells like it might be "yet another hack" that we have to maintain long term. The main reason being that we are trying to streamline method selection for our revised MOP (I

Re: JSR223 ScriptEngine not discovered with Release 2.4.7

Can you check the META-INF/services/javax.script.ScriptEngineFactory files within the two respective jars? Mine seem identical for those two releases. Also, what happens when you run this script in the groovyConsole: def factory = new javax.script.ScriptEngineManager() assert 'Groovy Scripting

Re: Groovy 3.0

not authorized to receive it, please promptly delete this > message and notify the sender by e-mail. Thank you. > > > On Jan 28, 2016, at 14:56, Paul King <pa...@asert.com.au> wrote: > > We are still working on getting 2.5 out the door. Only a little bit of > experim

Re: TeamCity JDK7 CI builds

There was a hung job that I killed. I also got rid of incubator from the repo url. Master seems to have built. Just waiting for the CI server to catch up on the 2_4_X branch. Cheers, Paul. On Sat, Jan 30, 2016 at 8:40 PM, Pascal Schumacher wrote: > It still does not

Re: Antlr4-based Groovy parser status update

, because it would conflict with the version of Groovy that we are > using, and apply global xforms on Groovy core. While it might be ok, we want > to minimize the risks. > > 2016-02-24 12:35 GMT+01:00 Paul King <pa...@asert.com.au>: >> >> Spock for testing is by no mean

Re: Where is Groovy's roadmap?

gt; 2016-01-19 20:10 GMT+01:00 Pascal Schumacher <pascalschumac...@gmx.net>: >> >> The roadmap document disappeared together with codehaus :( >> >> >> Am 19.01.2016 um 19:39 schrieb Aseem Bansal: >>> >>> Hi >>> >>> This came up during

Re: Preparing for a release

I looked into what would be needed to backport GROOVY-7427 and it turns out we'd need to bring across half of GROOVY-7087 as well. So, while it can be done, I am kind of -1 on such a change and +1 on getting the 2.5 beta out. Cheers, Paul. On Wed, Feb 17, 2016 at 8:29 AM, Cédric Champeau

Re: GROOVY-5727, removal of servlet-api from the zip distribution

+1 On 18 Apr 2016 8:22 pm, "Sergei Egorov" wrote: > +1 > > Currently forces some really nasty workarounds because of servlet-api > conflicts when Groovy CLI is being used. As well as jsp-api > > On Mon, Apr 18, 2016 at 1:19 PM daniel_sun > wrote: > >>

Re: Build broken for JDK9

There is a (broken since creation) jdk9 CI on teamcity: http://ci.groovy-lang.org/project.html?projectId=Groovy It needs some tlc. :-( The asciidoc generation should occur as part of install (does a maven-style install of jars including doc jars) task but not for the installGroovy task which

Re: groovy git commit: GROOVY-7876: ClassCastException when calling DefaultTypeTransformation#compareEqual (closes #368)

attention to some of the outstanding PRs around custom numbers if I get time. Cheers, Paul. On Mon, Jul 25, 2016 at 5:05 PM, Jochen Theodorou <blackd...@gmx.org> wrote: > On 24.07.2016 14:56, Paul King wrote: >> >> I think the GString check can be moved up as you suggest to impro

Re: groovy git commit: GROOVY-7876: ClassCastException when calling DefaultTypeTransformation#compareEqual (closes #368)

On Mon, Jul 25, 2016 at 5:05 PM, Jochen Theodorou <blackd...@gmx.org> wrote: > On 24.07.2016 14:56, Paul King wrote: >> >> I think the GString check can be moved up as you suggest to improve >> the readability of the code without breaking existing behavior, so >&

Re: groovy git commit: GROOVY-7876: ClassCastException when calling DefaultTypeTransformation#compareEqual (closes #368)

ge sounds more like a 3.0 thing. Cheers, Paul. On Fri, Jul 22, 2016 at 11:18 PM, Jochen Theodorou <blackd...@gmx.org> wrote: > > > On 22.07.2016 13:17, Paul King wrote: > [...] >> >> Which part could throw a ClassCastException above? > > > the compareTo

StaticCompileCastOptimizationTest

Does anyone know why StaticCompileCastOptimizationTest extends DefaultGroovyMethodsSTCTest and not just StaticTypeCheckingTestCase? I am presuming that StaticCompileDGMTest which also extends DefaultGroovyMethodsSTCTest handles the SC case for those tests. Thanks, Paul.

Re: Iterate ArrayList over XML Groovy

'..' is a shorthand for parent(), so the script removes unwanted nodes by removing them from their parent node. Cheers, Paul. On Sun, Aug 14, 2016 at 10:31 PM, GroovyBeginner wrote: > Thanks It worked!! what does refer in the script. Could you please explain > me the

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

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,

Re: [VOTE] Apache Groovy Roadmap

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

Re: [VOTE] Apache Groovy Roadmap

I kind of got the impression that the thread seemed to turn into a discussion thread - but happy to be corrected if others didn't get that impression. My impression was that there was a lot of consensus around what we want in the next "non-bugfix" release (e.g. macros and jdk 7+) but some

Re: 答复: About the performance of the test builds

I think it is a bit hard to compare those two numbers. Antlr4 grammar build steps are: gradlew test JDK8 Build steps are: gradlew clean test // with Indy gradlew clean test // without Indy And as a general comment, the CI server has numerous jobs that are kicked off from the main builds, so

Traits and protected properties

Hi, for traits we explicitly prohibit protected (and package private) methods - see the doco for some details. For properties however, we never check (in 2.4.7 and earlier) for that case (protected) and in fact include the property in the trait as if it was private. I was thinking of adding an

Re: release process

the src from 7 or running on 7. So probably some build changes and plugin capability. Cheers Paul. On 21 Jan 2017 5:01 AM, "Jochen Theodorou" <blackd...@gmx.org> wrote: > On 20.01.2017 13:14, Paul King wrote: > >> Wasn't the consensus to have parrot just in 3.0? S

Re: About a new annotation Groovydoc

I like the idea. I thought perhaps groovy.attach.annotation.groovydoc was a bit of a long prop name but I haven't thought of a better one yet. Cheers, Paul. On Fri, Feb 24, 2017 at 12:46 PM, Daniel Sun wrote: > Hi all, > > I am going to add a new annotation

Re: 2.4.9 release

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

[VOTE] Release Groovy 2.4.9

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=12339147 Tag:

2.4.9 release

I am ready to release 2.4.9. Last call for any changes/fixes you want in that release. Cheers, Paul.

Website deployment

Just a heads-up that the auto website publishing on the CI server was flakey last week - I spoke to a couple of you directly about it - but just to raise awareness I'll repeat here. It started failing a couple of days before I did the last release and without intervention (as far as I know) is

Re: 答复: next releases

Yes, the plan was always to create the 2_5_X branch before releasing 2.5.0-beta-1 and it makes sense to bump master to 3. If there is ever a need for a 2_6_X, that can come later. On Wed, Jan 18, 2017 at 8:22 PM, Cédric Champeau wrote: > I'm +1 on Andrés' plan.

Re: release process

Wasn't the consensus to have parrot just in 3.0? So we could make the 2_5_X branch now? On 20 Jan 2017 8:08 PM, "Jochen Theodorou" <blackd...@gmx.org> wrote: > > > On 19.01.2017 20:07, Paul King wrote: > >> +1 with a few comments below. >> >> Ther

Re: Convert Employee Node object to XML

You can use XmlNodePrinter directly. That is what serialize will use anyway: new XmlNodePrinter().print(node) Cheers, Paul. On Sun, Aug 21, 2016 at 3:03 AM, GroovyBeginner wrote: > I have Employee Node Object of class groovy.util.Node > > > > How to convert this

Re: Convert Employee Node object to XML Groovy

I'll forward your email to the users list. On Sun, Aug 21, 2016 at 5:06 PM, GroovyBeginner wrote: > I have Employee Node Object of class groovy.util.Node > > xml=Employees[attributes={}; value=[Employee[attributes={}; > value=[ID[attributes={}; value=[123]],

[RESULT][VOTE] Release Groovy 2.4.9

The Apache Groovy 2.4.9 vote is now closed and has passed with 4 binding +1s and no 0 or -1: Binding votes +1s: Paul King John Wagenleiter Guillaume Laforge Jim Jagielski The Apache Groovy community will proceed with the release. Thanks, The Apache Groovy Team

Re: [VOTE] Release Groovy 2.4.9

Doesn't appear to address GROOVY-4721 from my initial check. On Sun, Feb 26, 2017 at 7:21 PM, Jochen Theodorou wrote: > On 24.02.2017 11:14, Daniel Sun wrote: >> >> Hi Paul, >> >>If the PR(https://github.com/apache/groovy/pull/504) for fixing >> GROOVY-8085 is merged,

Re: Delete Sub Child XML Nodes

I forwarded your email to the users list since it isn't about development of the language codebase itself but rather about using Groovy. Cheers, Paul. On Thu, Aug 25, 2016 at 12:51 AM, GroovyBeginner wrote: > I am unable to delete the sub child xml Nodes. Here is the

Re: Proposal: Statically compileable builders

Sergei, I might try to find time shortly to produce a spike of a slightly improved transform similar to MapArguments. Are you happy for me to use parts of yours if needed? Cheers, Paul. On Wed, Oct 5, 2016 at 12:39 AM, Sergei Egorov wrote: > Hi Graeme, > > FYI a few years ago

Re: 答复: 答复: [PROGRESS REPORT 20161004]groovy-parser

I didn't realise Java 8 was a requirement. I was hoping we could maybe even sneak the new parser into Groovy 2.5 (but not turned on by default) since we have been delayed so long and the parser is coming along nicely. Given the Java 8 requirement, that might be a bit more work than we originally

Re: Groovy macro documentation

I'll try to review over the next little while too. Looks very promising at first glance! Exciting to see a good start! Paul. On Fri, Oct 7, 2016 at 9:17 PM, Guillaume Laforge wrote: > For reference, here's the PR: > https://github.com/apache/groovy/pull/439 > > On Fri, Oct

Re: Vote for a 2.5 BETA release

In terms of process, I think normally we prepare the release artefacts and vote on release of those artefacts. Cheers, Paul. On Fri, Sep 23, 2016 at 3:01 AM, Jochen Theodorou wrote: > > +1 > > following apache tradition this vote has to be at least 72h long... a > timespan we

Method resolution pondering

I am just wondering what people's thoughts are on the different approaches different parts of Groovy take for method resolution when multiple methods are matched. Given this code: import groovy.transform.CompileStatic interface FooA {} interface FooB {} class FooAB implements FooA, FooB

Re: JDK9 and the problem of @Grab

I guess I haven't looked into that part of JDK9 just yet. My first reaction would be to try to see what work would be involved with the "special handling". Keeping the existing behaviour (or close to it with perhaps a few caveats) would be ideal but has to be weighed up with the amount of work

Re: Method resolution pondering

t; On Sat, Aug 27, 2016 at 4:22 AM, Jochen Theodorou <blackd...@gmx.org> wrote: >> >> On 27.08.2016 12:22, Paul King wrote: >>> >>> I am just wondering what people's thoughts are on the different >>> approaches different parts of Groovy take for m

Re: Method reference for Groovy 3

nice! On Wed, Oct 26, 2016 at 6:29 AM, Jochen Theodorou wrote: > great stuff > > > On 25.10.2016 18:25, Daniel.Sun wrote: >> >> Hi all, >> >> The brand new parser can support method reference and constructor >> reference now. The implementation of backend is based on

Re: Lambda expression for Groovy 3

On Wed, Oct 19, 2016 at 8:25 PM, Guillaume Laforge wrote: > That's what I thought too. > Although there's one :: case that .& doesn't support in Groovy. > (details escape me at this point as I'm in a hurry to go & grab lunch :D) I think these are the references you had in

Re: About the parrot branch of apache/groovy

Hi Daniel. Do you have any trouble running the groovyConsole on the parrot branch? Won't start up for me. I'm travelling without access to proper internet. I might have just grabbed a snapshot at an inopportune time. On 11 Nov 2016 8:35 PM, "Guillaume Laforge" wrote: > Ok,

Re: Negative relational operators for Groovy 3

On Sat, Nov 19, 2016 at 12:16 AM, Graeme Rocher wrote: > In agreement with everyone else here. > > +1 to !in and !instanceof > -1 to everything else Same for me. I am undecided about sticky or not (allowing a space) but easier to be conservative and loosen later. I'm -1

Re: An issue about comparing arrays

We just have to be a little careful. Rightly or wrongly (search the mailing lists for many discussions), current Groovy's '==' tries to do 'friendly coercion' between types to try to give a business domain friendly meaning to equality: String[] one = ['a', 'b', 'c'] List two = ['a', 'b', 'c']

Re: About SimpleHTTPServer

I should have mentioned the above example is more about illustrating groovlets rather than serving up static content but it isn't too hard to switch between the two. On Sun, Dec 11, 2016 at 9:59 PM, Paul King <pa...@asert.com.au> wrote: > I don't know whether you would find listing 1

Re: About SimpleHTTPServer

I don't know whether you would find listing 12.16 from ReGinA useful: It is based on Jetty rather than com.sun.net.httpserver.HttpServer but might provide some useful inspiration: https://github.com/Dierk/GroovyInAction/blob/master/listings/chap12/Listing_12_16_GroovletExample.groovy Also, I

Re: [VOTE] Release Groovy 2.4.8

8.jar.asc) as > it does not exist. > > * Try: > Run with --stacktrace option to get the stack trace. Run with --info or > --debug option to get more log output. > > BUILD FAILED > --- > > > On Sun, Jan 8, 2017 at 10:33

Re: [VOTE] Release Groovy 2.4.8 - take 3

I am happy to announce that the vote has passed with four binding +1 votes and one non-binding +1 vote. Binding: Paul King, Guillaume Laforge, Jochen Theodorou, Cédric Champeau. Non-binding: Jacopo Cappellato. (We had additional +1s earlier on the same binary artifacts but the VOTE was restarted

ready for 2.4.8?

Hi everyone, I am ready to push out a 2.4.8 release. Any other last minute changes that need to be done? If I don't hear anything further, I'll do the first steps for the release (my) tomorrow and prepare some candidate artefacts and a [VOTE] thread. Cheers, Paul.

Re: [VOTE] Release Groovy 2.4.8

org> wrote: > On 31.12.2016 12:38, Paul King wrote: > [...] >> >> There is a 'gradleVersion' property (set in the build.gradle file) >> which is used when bootstrapping the wrapper, so no need for further >> instructions in that regard. > > > ah, ok. I am u

Re: [VOTE] Release Groovy 2.4.8

ion to be used for the > build? If not any gradle version will work we need to specify that in the > build instructions for the source distribution at least. > > bye Jochen > > On 31.12.2016 03:25, Paul King wrote: >> >> The README gives bootstrap instructions for buildin

Re: ready for 2.4.8?

Done. On Thu, Dec 29, 2016 at 8:56 AM, Paul King <pa...@asert.com.au> wrote: > It's a new feature but it seems fairly non-controversial. I guess we > could backport it. > > Cheers, Paul. > > On Thu, Dec 29, 2016 at 8:46 AM, Andres Almiray <aalmi...@gmail.com>

Re: [VOTE] Release Groovy 2.4.8

w wrapper" to update the wrapper jar > and gradlew scripts. If we don't need it anymore, I say we remove both the > property and wrapper.gradle. > > -Keegan > > On Sat, Dec 31, 2016 at 7:29 AM, Paul King <pa...@asert.com.au> wrote: >> >> I imagine some of them could

[VOTE] Release Groovy 2.4.8

Dear community, I am happy to start the VOTE thread for a Groovy 2.4.8 release! This release includes 82 bug fixes/improvements as outlined in the changelog: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12335950 Tag:

Re: [VOTE] Release Groovy 2.4.8 [CANCELLED]

gt; Assertion failed: > > assert 'Hello World' == 'hello world'.split(' ').collect{ it.uncapitalize() > }.join(' ') > > | | | | > > false | [hello, world] hello world > > [hello, world] > > > Am 30.12.2016 um 07:25 schrieb Paul King: > > Dear community, > &

Re: [VOTE] Release Groovy 2.4.8

it’s a pity! >> >> >> >> Uwe >> >> >> >> - >> >> Uwe Schindler >> >> Achterdiek 19, D-28357 Bremen >> >> http://www.thetaphi.de >> >> eMail: u...@thetaphi.de >> >> >> >>

Re: This was a surprise…

Thanks John. Yes, I should have a build-release process for testing later in the week. The reference to oss.jfrog.org will probably disappear in due course and point to our own repo. Cheers, Paul. On Mon, Dec 19, 2016 at 8:39 AM, Cédric Champeau wrote: > This looks

[VOTE] Release Apache Groovy 2.5.0-alpha-1 (take 2)

Dear community, I am happy to start the VOTE thread for a Groovy 2.5.0-alpha-1 release! This release includes 165 bug fixes/improvements as outlined in the changelog: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12338913 Tag:

[VOTE] Release Apache Groovy 2.5.0-alpha-1 (take 3)

Dear community, I am happy to start the VOTE thread for a Groovy 2.5.0-alpha-1 release! This release includes 165 bug fixes/improvements as outlined in the changelog: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12338913 Tag:

[CANCELLED][VOTE] Release Apache Groovy 2.5.0-alpha-1 (take 2)

t; ) > > Was caused by my recent change when I renamed extension module, sorry. > > I pushed a test fix. Assumption was incorrect, see the commit for an > explanation. > > On Wed, Mar 29, 2017 at 4:18 PM Paul King <pa...@apache.org> wrote: >> >> Dear community, >

Re: [VOTE] Release Apache Groovy 2.5.0-alpha-1

runtime.MacroGroovyMethods] > > > Is the groovy module missing its manifest or something? > > Guillaume > > > On Wed, Mar 29, 2017 at 6:06 AM, Paul King <pa...@apache.org> wrote: >> >> Dear community, >> >> I am happy to start the VOTE t

Maven coordinates going forward

Hi, it's still a little while away but we'll soon begin the work on what will be called Groovy 3 or Groovy 4 - the exact version number is potentially up for further debate depending on how other upcoming Parrot back port work pans out but we are not asking for feedback on that right now. This

Re: groovy git commit: Add build scans to 2.4 branch

Fixed On Tue, Mar 14, 2017 at 9:59 PM, Paul King <paul.king.as...@gmail.com> wrote: > Hi Cédric, the commit below breaks the JDK 6 build: > java.lang.UnsupportedClassVersionError: > me/champeau/gradle/buildscans/RecipesPlugin : Unsupported major.minor > version 51.0 > > O

Re: Groovy getting Fat?

There have been requests to include the docs in the release which explains the difference in size. I was going to include a note on that when I send out the announce email shortly asking for feedback. If folks don't like the extra size, we'll need to create a groovy-extras or groovy-docs separate

[ANNOUNCE] Apache Groovy 2.4.10 Released

Dear community, The Apache Groovy team is pleased to announce version 2.4.10 of Apache Groovy. Apache Groovy is a multi-facet programming language for the JVM. Further details can be found at the http://groovy.apache.org website. This release is a maintenance release of the GROOVY_2_4_X branch.

[RESULT][VOTE] Release Apache Groovy 2.4.10 (take 2)

The result has passed with 3 binding and 3 non-binding votes. There were additional binding and non-binding votes from take 1, but we don't officially need those so I won't count them. But thanks everyone for voting. Binding votes: Paul King Cédric Champeau Guillaume Laforge I'll kick off

[VOTE][LAZY] Apache Groovy Roadmap - take 2

Hi folks, Earlier in the year, Cédric did a great job of outlining a possible roadmap for Groovy. I think there was general consensus on most of it but we never quite managed complete consensus. We had a fairly clear consensus on getting out 2.5 with macro support - that is underway now. There

Re: upcoming releases

Just a slight deviation to below. The version number on master has temporarily been set to 2.9.98-SNAPSHOT pending Spock support of Groovy 3+ version numbers. Cheers, Paul. On Wed, Mar 15, 2017 at 10:17 AM, Paul King <pa...@asert.com.au> wrote: > I have created the 2_5_X branch. I

[ANNOUNCE] Apache Groovy 2.5.0-alpha-1 Released

Dear community, The Apache Groovy team is pleased to announce version 2.5.0-alpha-1 of Apache Groovy. Apache Groovy is a multi-facet programming language for the JVM. Further details can be found at the http://groovy.apache.org website. This is a pre-release of a new version of Groovy. We

[RESULT][VOTE] Release Apache Groovy 2.5.0-alpha-1 (take 3)

The vote has passed with 3 binding votes: Paul King Guillaume Laforge John Wagenleitner There was also 3 non-binding votes and additional votes cast during earlier candidates. I'll proceed with deploying the release. Cheers, Paul. On Thu, Mar 30, 2017 at 3:49 PM, Paul King <pa...@apache.

Re: Nextflow joint build

wrote: > Interesting, all nextflow tests are green with 2.5.0-SNAPSHOT but I'm > getting several failures with 2.5.0-alpha-1 > > p > > > On Wed, Apr 5, 2017 at 9:18 AM, Paolo Di Tommaso < > paolo.ditomm...@gmail.com> wrote: > >> Thanks! >> >&g

Re: 答复: About the performance between master and GROOVY_2_5_X

I was also going to look at that too but have lots more on my todo list first. I was going to do that after creating the GROOVY_2_6_X branch. I'll try to do the GROOVY_2_6_X branch today which then leaves master ready for jdk8 only and parrot as the default - happy for you to look at this Daniel.

Re: 答复: About the performance between master and GROOVY_2_5_X

OK, the GROOVY_2_6_X branch is created. It possibly needs a little tidy up and I haven't attempted merging the backport yet. But master is all set for jdk8+ and changes to make parrot the default. Cheers, Paul. On Fri, Apr 21, 2017 at 2:57 PM, 孙 岚 wrote: > Hi Paul, >

Fwd: Raising my hand

Just forwarding - didn't realise it wasn't to the list. -- Forwarded message -- From: Paul King <pa...@asert.com.au> Date: Thu, Apr 20, 2017 at 1:19 PM Subject: Re: Raising my hand To: Yazad Khambata <yaz...@gmail.com> Updating the ticket would be great. We can repo

Re: Raising my hand

Hi Yazad, We are always keen to see progress being made on the code base. GROOVY-1200 looks a little old and I wonder whether some of the functionality is already in place. I left a comment on the issue suggesting we review what was being asked for in that issue and what is currently supported.

[VOTE] Release Apache Groovy 2.4.10

Dear community, I am happy to start the VOTE thread for a Groovy 2.4.10 release! This release includes 9 bug fixes/improvements as outlined in the changelog: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12339743 Tag:

[VOTE] Release Apache Groovy 2.4.10 (take 2)

Dear community, I am happy to (re)start the VOTE thread for a Groovy 2.4.10 release! This release has the problematic stricter method checking (GROOVY-6792) disabled by default but it can be enabled with a system property. Thanks John for spotting the potential problem. Even though I think it

Re: [VOTE] Release Apache Groovy 2.4.10

which may not depending on how you run it - like the test you showed. Cheers, Paul. On Mon, Mar 13, 2017 at 10:38 AM, Paul King <pa...@asert.com.au> wrote: > Hi John, the Spock example is fine since that isn't left as the method > name by the time the test is run. I am puzzled how t

Re: [VOTE] Release Apache Groovy 2.4.10

te: >> >> I'm tempted to send a +1, I've checked the signatures, but I have a weird >> error when building: https://scans.gradle.com/s/hgptywcc26pq2 >> >> Has anyone seen this before? >> >> 2017-03-10 19:51 GMT+01:00 Bahman Movaqar <bah...@bahmanm.c

Re: [VOTE] Release Apache Groovy 2.4.10

I couldn't replicate on Ubuntu or Windows using 1.8.0_121. On Sat, Mar 11, 2017 at 3:18 PM, Paul King <pa...@asert.com.au> wrote: > What Java version are you using Guillaume? > > On Sat, Mar 11, 2017 at 6:45 AM, Guillaume Laforge <glafo...@gmail.com> wrote: >>

Re: Groovy 2.5 SNAPSHOT and final local variables

I noticed a few similar problems recently (GROOVY-8093, GROOVY-8094) but yours looks slightly different again. Probably worth creating an issue. On Sun, Mar 5, 2017 at 11:16 PM, Alain Stalder wrote: > Not sure if this is the right/best place to report this, but I got this with

upcoming releases

Hi, I am planning to merge PR#508 and start the release process for 2.4.10 over the next few days. This contains an important bug fix that affects downstream projects such as Grails. Any other fixes people want in that release? Soon after that is released I am planning to create a 2_5_X branch

Re: finally success again on JDK9

Good news Jochen! >From what I understand, the --permit-illegal-access option will be gone for JDK10+, so we need to keep looking at further restructuring/rework at some point down the track. Is that also your understanding? It definitely buys us more time though. Cheers, Paul. On Fri, Apr 7,

imminent 2.4.11 release

I will send out the vote email for 2.4.11 (my) tomorrow. If anyone wants to quickly check the artifacts in the meantime, please feel free: https://dist.apache.org/repos/dist/dev/groovy/2.4.11 Cheers, Paul.

[VOTE] Release Apache Groovy 2.4.11

Dear community, I am happy to start the VOTE thread for a Groovy 2.4.11 release! This release includes 11 bug fixes/improvements as outlined in the changelog: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12340047 Tag:

Re: RAT Unapproved License Error when building

I'm on holidays without laptop but from memory there is a list of exclusions when we call the rat gradle plugin. But in this case we should possibly try to configure testng so that test-output appears under target. Then an existing exclusion should work. On 3 Jul. 2017 5:15 am, "Yazad Khambata"

Re: moving the Groovy website

with the code - I'm talking about the fairly static pages on the site (downloads, events, mailing-lists, etc.). Thanks, Paul. On Wed, Apr 26, 2017 at 7:57 AM, Paul King <pa...@asert.com.au> wrote: > > One of the action items we've had since joining Apache is to move our > webs

Re: moving the Groovy website

to the website. > > On Wed, Apr 26, 2017 at 12:30 AM, Paul King <pa...@asert.com.au> wrote: > >> One question I have. How important is the git history of the website? Is >> a clean slate copy of all the files to the new repo acceptable? I'd never >> want to do

Re: [VOTE] Release Apache Groovy 2.4.11

> A. > > On Tue, Apr 25, 2017 at 11:30 AM, Cédric Champeau <cchamp...@apache.org> > wrote: > >> +1 (binding) >> >> 2017-04-25 0:09 GMT+02:00 Paul King <pa...@asert.com.au>: >> >>> Dear community, >>> >>> I am happy to

Re: [VOTE] Release Apache Groovy 2.4.11

a92c7/grails-datastore-core/sr > c/main/groovy/org/grails/datastore/mapping/dirty/checking/Di > rtyCheckable.groovy > > On Mon, Apr 24, 2017 at 3:09 PM, Paul King <pa...@asert.com.au> wrote: > >> Dear community, >> >> I am happy to start the VOTE thread for

[CANCELLED][VOTE] Release Apache Groovy 2.4.11

As per previous message, I'll cancel and re-try. Cheers, Paul. On Thu, Apr 27, 2017 at 12:20 AM, Paul King <pa...@asert.com.au> wrote: > I think John that it is because of the GROOVY-8127 bug that those tests > are failing. The datastoreVersion of 6.1.1 will be built with a version

Re: [VOTE] Release Apache Groovy 2.4.11

parameter and I couldn't actually trigger an error with the bad value in place (optimised away?) but in the interests of being conservative I will re-cut the build. Cheers, Paul. On Wed, Apr 26, 2017 at 7:09 PM, Paul King <pa...@asert.com.au> wrote: > John, what steps are you usin

Re: [VOTE] Release Apache Groovy 2.4.11

It seems to be hard > given the 48h vote. Basically cancelling this vote forces us to release > Gradle 4.0-milestone-1 with a snapshot version of Groovy (duh). > > 2017-04-26 17:08 GMT+02:00 John Wagenleitner <john.wagenleit...@gmail.com> > : > >> Hi Paul, >> >

[VOTE] Release Apache Groovy 2.4.11 (take 2)

are cast. [ ] +1 Release Apache Groovy 2.4.11 [ ] 0 I don't have a strong opinion about this, but I assume it's ok [ ] -1 Do not release Apache Groovy 2.4.11 because... Here is my vote: +1 (binding) On Thu, Apr 27, 2017 at 1:50 AM, Paul King <pa...@asert.com.au> wrote: > Hi Cédric, &g

Re: [VOTE] Release Apache Groovy 2.4.11 (take 2)

As per Cédric's request, I'd like to make the release window 36hrs, so I'll target 36hrs assuming I get enough votes by then (unless there are any objections). Cheers, Paul. On Thu, Apr 27, 2017 at 1:55 AM, Paul King <pa...@asert.com.au> wrote: > Dear community, > > I am

[RESULT][VOTE] Release Apache Groovy 2.4.11 (take 2)

The vote has passed with 5 binding +1 votes and 3 non-binding +1 votes. There were additional +1 votes on the previous candidate which was almost the same. Cheers, Paul. On Thu, Apr 27, 2017 at 1:55 AM, Paul King <pa...@asert.com.au> wrote: > Dear community, > > I am happy to

Re: Help with task: Groovydoc improved comment extraction

Hi Shanu, When I created that task I forgot about a little bit of internal work we need to do first before anyone can easily assist. But we'd be keen for you to help with something. I'll try to include a couple more tasks in the helpwanted list over the next week. Cheers, Paul. On Fri, Aug 4,

additional jira tweaks

Hi everyone, We were using 3.0 within Jira as a version both for scheduling future work and for some recent parrot fixes. I have moved the fixes to 3.0.0-alpha-1 (we can rename later to beta-1 if we skip alpha-1) and the scheduled work to 3.x. Similarly, we had 4.0 for scheduled future work. That

Mini roadmap

Hi everyone, We are asked from time to time about Groovy's roadmap (e.g. [1]). Having a roadmap is conceptually a very attractive idea. It helps us plan our releases and reminds us of our big ticket items we are wanting to do going forward. It also helps users of the language do their planning.

  1   2   3   4   5   6   7   8   9   10   >