Re: Want to start contributing to the community

Hi Anantha, please have a look at http://groovy-lang.org/contribute.html Cheers, Pascal Am 04.12.2015 um 09:25 schrieb ANANTHA KAILASH: Hello team, I am kailash from India. I am very much interested to start contributing to the open source community and chose Groovy language to start with. I

Re: [Mentors/Guillaume] John Wagenleiter missing JIRA rights

Hello everybody, sorry to nag, but has somebody already granted John the rights? Thanks, Pascal Am 01.12.2015 um 19:30 schrieb Pascal Schumacher: Hello everybody, it would be very nice if somebody could grant John the missing JIRA rights. Thanks, Pascal Weitergeleitete Nachricht

Re: Tests failing locally

Hi Rahul, the tests pass for me locally, but if my memory serves me correctly the *ExtensionModuleTests did fail on teamcity recently due to a corrupted grape directory. Try deleting "~/.groovy/grapes", maybe this helps. ExecuteTest is one fragile tests that use sleep(), so it fails form time

"Official" link for groovy becoming a top level project?

Hello everybody, is there some "official" statement that groovy is now a top level project? People still seem to be unaware of the fact that we graduated e.g. http://mail-archives.apache.org/mod_mbox/jmeter-dev/201512.mbox/%3CCACTiXJpf7JHUqpepqfAJmpHYkKd9GAG%3D1%3DdZKeY0aGQPfuJXSg%40mail.gmail.

Re: Help improving the groovy compiler?

Hi Estaban, sorry for the late reply. :( You have a look at the JIRA issues of the compiler components: https://issues.apache.org/jira/issues/?jql=project%20%3D%20GROOVY%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20Compiler%20ORDER%20BY%20priority%20DESC https://issues.apache

Re: Release 2.4.6 and 2.5.0-beta?

I'll contact back the guys about this, to make sure they follow the discussions. 2015-11-28 11:04 GMT+01:00 Pascal Schumacher <mailto:pascalschumac...@gmx.net>>: Hello everybody, what about (a) new release(s) to celebrate becoming top level project? There are already 3

Re: Release 2.4.6 and 2.5.0-beta?

I'll be at GGX London next week, so I'll try to find some time. 2015-12-10 21:59 GMT+01:00 Graeme Rocher <mailto:graeme.roc...@gmail.com>>: Please could my pull requests be merged before 2.4.6? On 10 Dec 2015, at 19:29, Pascal Schumacher mailto:pascalschumac...

Re: Welcome to the ASF

Hi Carl, thanks for the warm welcome and welcome to the mailing list. :) Cheers, Pascal Am 23.12.2015 um 18:02 schrieb Carl Marcum: I would like to offer my unofficial welcome to Apache !! I'm a big Groovy fan and it's my favorite language. I commit when I can to the OpenOffice project, most

Re: Groovy missing on www.apache.org

Hi Roman, thanks for creating the file. I merged the pull request. I guess this: https://git-wip-us.apache.org/repos/asf?p=groovy.git;f=DOAP.rdf;a=blob_plain;hb=HEAD should be added to files.xml according to http://projects-old.apache.org/create.html Thanks, Pascal Am 23.12.2015 um 21:57 s

Re: Dropping GROOVY-7432

Hi Peter, as you tried to implement the enhancement, you are in the best position to judge if it makes or does not. If you think the issue should be closed, we should close it. Cheers, Pascal Am 24.12.2015 um 10:19 schrieb Peter Ledbrook: Hi, I'm thinking of closing the above issue as Won'

Re: Github pull requests not picked up by CI server

Hi John, I believe nobody changed the pull request job?, so I guess it's best to raise an issue with infra: https://issues.apache.org/jira/browse/INFRA/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel to check if there is an issue with the github integrations/hook. Cheers,

Re: Github pull requests not picked up by CI server

As it is still not working (I checked by force pushing a pull request) I created a issue with infrastructure: https://issues.apache.org/jira/browse/INFRA-11004 Am 27.12.2015 um 09:25 schrieb Pascal Schumacher: Hi John, I believe nobody changed the pull request job?, so I guess it's bes

Fwd: Re: Github pull requests not picked up by CI server

Ticket is solved. Your PRs are building. :) Weitergeleitete Nachricht Betreff:Re: Github pull requests not picked up by CI server Datum: Mon, 28 Dec 2015 08:37:55 +0100 Von:Pascal Schumacher Antwort an: dev@groovy.apache.org, dev@groovy.apache.org An: dev

Re: Release 2.4.6 and 2.5.0-beta?

e idea, so he may remember :) 2015-12-22 8:20 GMT+01:00 Pascal Schumacher mailto:pascalschumac...@gmx.net>>: Hi Cédric, any updates concerning the release? Thanks, Pascal Am 11.12.2015 um 12:51 schrieb Cédric Champeau: Yes

Re: Groovy missing on www.apache.org

y not completed yet? Cheers, Pascal Am 23.12.2015 um 23:34 schrieb Roman Shaposhnik: On Wed, Dec 23, 2015 at 1:38 PM, Pascal Schumacher wrote: Hi Roman, thanks for creating the file. I merged the pull request. Great! I guess this: https://git-wip-us.apache.org/repos/asf?p=groovy.

Re: groovy git commit: Fixing squid:S2444 - Lazy initialization of "static" fields should be "synchronized"

Yes, I agree the change most likely reduces performance, but increases thread-safety (prevent that different Threads may work with different Metaclasses etc.) I do not know enough about this area of the code to judge if the lack of thread-safety is really a concern. I just merged the pull r

Re: groovy git commit: Fixing squid:S2444 - Lazy initialization of "static" fields should be "synchronized"

at 2:45 PM, Pascal Schumacher mailto:pascalschumac...@gmx.net>> wrote: Yes, I agree the change most likely reduces performance, but increases thread-safety (prevent that different Threads may work with different Metaclasses etc.) I do not know enough about this area of the code

Re: Groovy missing on www.apache.org

:-( https://svn.apache.org/repos/asf/comdev/projects.apache.org/README_NEWTLP On top of which the new ones don't quite work for me just yet. Stay tuned -- I'm figuring it out with sebb now. Thanks, Roman. On Sat, Jan 2, 2016 at 2:52 PM, Pascal Schumacher wrote: http://www.apache.org/

GROOVY-7378: Support JAVA_OPTS containing quoted arguments on *nix

Hello everybody, is there anybody with unix shell scripting know-how who would be so kind to take a look at the pull request: https://github.com/apache/groovy/pull/5 for https://issues.apache.org/jira/browse/GROOVY-7378 and offer some feedback as to whether it should be merged? Thanks in ad

Disable auto-assignment of jira issues?

Hello everybody, I think should disable auto-assignment of jira issues. Dozen of issues are assigned to people who do not currently work on them. I believe this stops people from contributing, because they think somebody is already working on the issue. It also mislead users to expect that the

Normalize line endings?

Hello everybody, should the line endings of all source files in git be normalized to "\n"? see the discussion at https://github.com/apache/groovy/pull/236 -Pascal

Re: "Official" link for groovy becoming a top level project?

Mon, Dec 7, 2015 at 12:30 PM, Pascal Schumacher wrote: Hello everybody, is there some "official" statement that groovy is now a top level project? Well there are board meeting notes ratifying the decision. That's as official as it gets. If what you mean is PR -- I don't think

Re: Disable auto-assignment of jira issues?

Am 16.01.2016 um 06:06 schrieb Guillaume Laforge: I've moved forward and removed all component leads, and set back the default assignment to the "default project assignment" which is... "no assignment". So we're good now on that front. Thanks! Perhaps the next step would be to do a pass on all

Re: Disable auto-assignment of jira issues?

d issues and remove all assignments? The problem with that though is that doing it large and wide might remove assignments that are indeed really being worked on... What do you think? Guillaume On Fri, Jan 15, 2016 at 7:42 PM, Pascal Schumacher mailto:pascalschumac...

Re: Builld on JDK9

I guess that's be a consequence of me merging the two asciidoc asset locations into on with https://github.com/apache/groovy/commit/f2a2fc05951a72335e60cbb97231cdc1dd91709c Should be fixed by https://github.com/apache/groovy/commit/bdaef2a1539d3b3d0a9a5fa549ddd7421673797f Thanks for reportin

Re: Groovy missing on www.apache.org

http://www.apache.org/index.html#projects-list now lists grooy Thanks! :) Am 18.01.2016 um 07:57 schrieb Roman Shaposhnik: Done! On Thu, Jan 14, 2016 at 1:15 PM, Pascal Schumacher wrote: Hi Roman, any updates? https://projects.apache.org/project.html?groovy now shows the DOAP file, but

Re: Where is Groovy's roadmap?

The roadmap document disappeared together with codehaus :( Am 19.01.2016 um 19:39 schrieb Aseem Bansal: Hi This came up during gr8conf India. I asked Paul King and he said that to ask the community so it is known. I tried looking for groovy's roadmap but couldn't find anything. Where is it

Re: Which file is the adoc for contributions?

it's not in the repo anymore, because wasn't integrated with the rest of the documentation or the website, wasn't up-to-date and duplicated http://www.groovy-lang.org/contribute.html Am 19.01.2016 um 21:40 schrieb Aseem Bansal: I mean for the URL http://docs.groovy-lang.org/next/html/documenta

Remove http://www.groovy-lang.org/groovy-weekly.html ?

Hello everybody, since the weekly newsletter is dead (last issue was over four months ago: http://us4.campaign-archive2.com/home/?u=cb8b56e9d6a1cb1696cecc673&id=1a76961630) should we remove http://www.groovy-lang.org/groovy-weekly.html ? -Pascal

Re: Remove http://www.groovy-lang.org/groovy-weekly.html ?

ite a bit of work to collect and curate all the interesting bits of news (3+ hours a week) There are 1000+ subscribers to this mailing-list, so it's worthwhile keeping it alive. Guillaume On Tue, Jan 19, 2016 at 11:04 PM, Pascal Schumacher wrote: Hello everybody, since the weekly newslette

Re: Remove http://www.groovy-lang.org/groovy-weekly.html ?

URL of the page, I'm wondering about the Google Search indexing... OTOH, Google Search will update the link at some point. What do you think? On Wed, Jan 20, 2016 at 8:20 AM, Pascal Schumacher wrote: Nice to hear :) Then we should just rename it to groovy biweekly/monthly or just groovy newsl

Re: Where is Groovy's roadmap?

n have a 3 to 6 months roadmap, but anything longer is unrealistic. 2016-01-19 20:10 GMT+01:00 Pascal Schumacher : The roadmap document disappeared together with codehaus :( Am 19.01.2016 um 19:39 schrieb Aseem Bansal: Hi This came up during gr8conf India. I asked Paul King and he said that to as

Re: Disable auto-assignment of jira issues?

I went ahead and removed the assignee of all issue which didn't look like they were currently worked on. Am 16.01.2016 um 13:11 schrieb Pascal Schumacher: Am 16.01.2016 um 06:06 schrieb Guillaume Laforge: I've moved forward and removed all component leads, and set back the default

Re: Which file is the adoc for contributions?

reached that out of date page On Wed, Jan 20, 2016 at 2:21 AM, Pascal Schumacher mailto:pascalschumac...@gmx.net>> wrote: it's not in the repo anymore, because wasn't integrated with the rest of the documentation or the website, wasn't up-to-date and duplicated http:

Re: Which file is the adoc for contributions?

Am 22.01.2016 um 17:26 schrieb Aseem Bansal: @Pascal Maybe I am missing something but if it is not in the repository then how does the URL http://docs.groovy-lang.org/next/html/documentation/groovy-contributions.html show the version Version 2.5.0-SNAPSHOT? I do not know. In earlier versions o

Re: TeamCity JDK7 CI builds

It still does not work. There are 490 pending build for this job. :( @Cédric, @Paul: I guess you are the only ones with access to the build server. It would be nice if you could check what is wrong. Thanks, Pascal Am 28.01.2016 um 18:32 schrieb John Wagenleitner: The TC builds for JDK7 haven'

Re: TeamCity JDK7 CI builds

30, 2016 at 8:40 PM, Pascal Schumacher wrote: It still does not work. There are 490 pending build for this job. :( @Cédric, @Paul: I guess you are the only ones with access to the build server. It would be nice if you could check what is wrong. Thanks, Pascal Am 28.01.2016 um 18:32 schrieb

Re: Release 2.4.6 and 2.5.0-beta?

mCity, and rely on Gradle build scripts instead. Stay tuned. Am 02.01.2016 um 17:10 schrieb Pascal Schumacher: > As I was not present at the conference I can not follow the discussion, but we should really release 2.4.6. There now there are 61 issues fixed: > > https://issues.apa

Should the pull request for "GROOVY-7735 - Closures should be generated as public classes" be merged?

Hello everyone, any objections to a merge of: https://github.com/apache/groovy/pull/248 Requested in https://issues.apache.org/jira/browse/GROOVY-7735 ? Cheers, Pascal

Re: Should the pull request for "GROOVY-7735 - Closures should be generated as public classes" be merged?

sure should this be in 2.4.6, or master only? Am 06.02.2016 um 09:15 schrieb Jochen Theodorou: On 03.02.2016 18:12, Pascal Schumacher wrote: Hello everyone, any objections to a merge of: https://github.com/apache/groovy/pull/248 Requested in https://issues.apache.org/jira/browse/GROOVY-7735

Re: Should the pull request for "GROOVY-7735 - Closures should be generated as public classes" be merged?

done Am 08.02.2016 um 08:23 schrieb Jochen Theodorou: I am thinking we could do it for both. If then 2.4.6 breaks we will have to undo the change and I prefer knowing this now, than in a 2.5.x version bye Jochen

Re: Preparing for a release

Hi Cédric, great news. :) I think before https://issues.apache.org/jira/browse/GROOVY-7742 should be resolved, by either applying https://github.com/apache/groovy/pull/253 or reverting https://github.com/apache/groovy/commit/fae29119a1102393ae5d1645c3fc1e06547b0ad8 If nobody more qualified

Re: Preparing for a release

I fixed https://issues.apache.org/jira/browse/GROOVY-7742 by reverting as Shils and John suggested in the discussion of https://github.com/apache/groovy/pull/253 Am 15.02.2016 um 22:12 schrieb Pascal Schumacher: Hi Cédric, great news. :) I think before https://issues.apache.org/jira/browse

Re: Preparing for a release

y piece of String.metadata function ? thx ​jim ​ On 16 February 2016 at 08:12, Pascal Schumacher mailto:pascalschumac...@gmx.net>> wrote: I fixed https://issues.apache.org/jira/browse/GROOVY-7742 by reverting as Shils and John suggested in the discussion of https://github.com/apache

Re: Preparing for a release

oo worried about back-porting this one. Other opinions? Cheers, Paul. On Wed, Feb 17, 2016 at 6:02 AM, John Wagenleitner wrote: Hi Jim, I think the file you might be looking for is: src/main/org/codehaus/groovy/runtime/StringGroovyMethods.java On Tue, Feb 16, 2016 at 10:36 AM, Pascal

Re: Preparing for a release

Am 16.02.2016 um 22:56 schrieb chrylis: Do you consider all micros to be "bugfix releases", or are some of them fixes and some of them small enhancements? In Groovy, there's a tendency for minor updates to require cascading changes to other components (e.g., GRECLIPSE, Spock). From 2.0 on the

Re: [VOTE] Release Apache Groovy 2.4.6

+1 md5 and signature are correct All test pass and I could build the binaries from source. Thanks a lot Cédric. Cheers, Pascal Am 18.02.2016 um 22:27 schrieb Cédric Champeau: Dear community, I am happy to start the VOTE thread for a Groovy 2.4.6! This release includes a lot of bugfixes sin

Re: [VOTE] Release Apache Groovy 2.4.6

Hi Konstantin, thanks for the in-depth check. :) Am 19.02.2016 um 08:49 schrieb Konstantin Boudnik: - gradle.properties is missing the ASL header and breaking the rat check. I figure this alone doesn't warrant a respin, but the header needs to be added or the file needs to be excluded fro

JDK 9 Indy Test Failures

Hello everybody, since a few weeks the "normal" groovy build and tests pass on JDK9. But when invoke-dynamic is used some groovy-sh tests fail: http://ci.groovy-lang.org/viewLog.html?buildId=31836&tab=buildResultsDiv&buildTypeId=Groovy_Jdk9Build&guest=1 with: java.lang.IncompatibleClassChange

Automated Testing of Pull Request

Hello everybody, the testing of pull request on https://builds.apache.org/view/Groovy/job/Groovy%20Github%20PRs/ often failed with errors unrelated to the pull request. This was confusing our contributors, e.g.: https://github.com/apache/groovy/pull/256 https://github.com/apache/groovy/pull/

Re: Failing tests [Was: [VOTE] Release Apache Groovy 2.4.6]

2016 at 05:12PM, Konstantin Boudnik wrote: Hi Pascal. The logs are gone, but I will attempt to rerun the tests and share the stacktraces via JIRA. Cheers, Cos On Sun, Feb 21, 2016 at 01:25PM, Pascal Schumacher wrote: Hi Konstantin, thanks for the in-depth check. :) Am 19.02.2016 um 08:49 sch

Re: [GitHub] groovy pull request: Link to MrHaki's blog in TupleConstructor jav...

Well it's not really hidden, as the groovy/javadoc is published on the web and quite high in the google search results (at least for me). Also you can configure e.g. Eclipse to automatically download sources and javadocs for all dependencies, so it's directly visible in the IDE. Cheers, Pasca

Re: More Antlr4-based Groovy parser status update

Hi Jesper, thanks for the update. :) Nice to hear you are progressing. Concerning the ASTBuilder to Java conversion, there is a pull request with this at the old repo https://github.com/groovy/groovy-core/pull/513 Cheers, Pascal Am 28.02.2016 um 12:55 schrieb Jesper Steen Møller: Hi Groovy-

Aw: Re: More Antlr4-based Groovy parser status update

y.apache.org Betreff: Re: More Antlr4-based Groovy parser status update Hi Pascal,   Thank you, I’d missed that one.   Any thought on the validity of “- -1”?   -Jesper   On 28. feb. 2016, at 18.23, Pascal Schumacher <pascalschumac...@gmx.net> wrote:   Hi Jesper, thanks for the u

Release 2.5 Beta?

Hello everybody, as far as I remember there was wide support for releasing a 2.5 beta in the "Release 2.4.6 and 2.5.0-beta?" discussion. The release announcement for 2.4.6 contained the sentence "... be prepared for a 2.5.0-beta release soon!". Tomorrow that will be two weeks ago, so I think

Re: Release 2.5 Beta?

Hi Nick, Am 12.03.2016 um 00:05 schrieb Nicholas Grealy: Just some questions for the broader dev community: * Who can perform the release? As far as I know Guillaume, Jochen und Paul should also have the necessary knowledge and access rights to do a release. * Is there anything outstand

http://ci.groovy-lang.org/ - "The TeamCity license will expire in 10 days."

Hello everybody, the TeamCity license of http://ci.groovy-lang.org/ will expire soon. - Pascal

http://www.groovy-lang.org/ down

Hello everybody, http://www.groovy-lang.org/ seems down since Friday?

Re: Problem creating groovy-macro spec files

Hi Mario, as far as I remember groovy-macro is global ast-transformation. I guess here is some side-effect/bug which causes the test failures. Sadly I lack the necessary knowledge to investigate further. -Pascal Am 22.05.2016 um 14:33 schrieb Mario Garcia: Hi: I'm trying to write some exam

Re: 2.4.7 Release?

+1000 to both a 2.4.7 and a 2.5-Beta release Am 20.05.2016 um 15:25 schrieb Cédric Champeau: A new release would be timely. Maybe we can try to get the 2.5 beta out too, would be nice for GR8Conf! What other fixes are in 2.4.7? 2016-05-20 14:34 GMT+02:00 Guillaume Laforge

Re: Travis

Hi Jochen, as far as I know it's not possible. The only way to rerun a build on travis is to push to the pull request (easiest way: "commit --amend", "push -f"). Cheers, Pascal Am 30.06.2016 um 22:15 schrieb Jochen Theodorou: Hi all, I just tried to rerun a build on travis (the instance re

Release 2.4.8 ?

Hello everyone, Paul and John fixed a lot of issues recently, so there are now 44 fixed issues: https://issues.apache.org/jira/issues/?jql=project%20%3D%20GROOVY%20AND%20fixVersion%20%3D%202.4.8%20AND%20status%20%3D%20Resolved%20ORDER%20BY%20priority%20DESC The last release was three months a

Re: getting in line for the releases of groovy 2.4.8 and 2.5.0-beta-1

+1 for releasing 2.4.8 as soon as possible. There are already 67 fixed issues: https://issues.apache.org/jira/issues/?jql=project%20%3D%20GROOVY%20AND%20fixVersion%20%3D%202.4.8%20ORDER%20BY%20status%20DESC%2C%20priority%20DESC Am 19.10.2016 um 16:32 schrieb Jochen Theodorou: Hi, I´dd like to

Re: Double posts

There were a lot of double post recently, because the following header was used: To: dev@groovy.apache.org Cc: Groovy_Developers I guess it was caused by somebody sending mails to d...@groovy.incubator.apache.org, which the list forwards with "Reply-To: dev@groovy.apache.org". Then people/

Re: Fate of TailRecursive

it hasn't been removed Am 26.11.2016 um 12:04 schrieb Johannes Link: Unless it has been removed again it should still be in core. Von meinem iPad gesendet Am 26.11.2016 um 11:13 schrieb Andres Almiray : Didn't it get merged into Groovy core after some time living as an external download? S

Re: [VOTE] Release Groovy 2.4.8

Hello Paul, thanks a lot for volunteering as a release manager. :) Sadly the javadoc of StringGroovyMethods#uncapitalize contains an error so, the unit tests fail with: MainJavadocAssertionTest > StringGroovyMethodsJavadocAssertionTest.testAssertionFromStringGroovyMethodsLine213 FAILED As