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

+1 (binding) On Sun, Jul 19, 2020 at 5:36 AM Paul King wrote: > > [Sorry for the glitch, let's try that again!] > > Dear development community, > > I am happy to start the VOTE thread for a Groovy 3.0.5 release! > > This release includes 74 bug fixes/improvements as outlined in the > changelog:

Re: [VOTE] Release Apache Groovy 2.4.20

+1 (binding) On Sat, Jul 18, 2020 at 4:47 PM Paul King wrote: > > Dear development community, > > I am happy to start the VOTE thread for a Groovy 2.4.20 release! > > This release includes a handful of tweaks to the documentation and 2 bug > fixes/improvements as outlined in the changelog: > >

Re: [VOTE] Release Apache Groovy 2.5.13

+1 (binding) On Sat, Jul 18, 2020 at 8:14 PM Paul King wrote: > > Dear development community, > > I am happy to start the VOTE thread for a Groovy 2.5.13 release! > > This release includes 39 bug fixes/improvements as outlined in the > changelog: > >

Re: [VOTE] Release Apache Groovy 3.0.1

+1 (binding) On Fri, Feb 14, 2020, 2:07 AM Paul King wrote: > > Dear development community, > > I am happy to start the VOTE thread for a Groovy 3.0.1 release! > There was a glitch in the Groovy binaries in the 3.0.0 release so > I thought it prudent to get this out sooner rather than later. >

Re: [VOTE] Release Apache Groovy 3.0.0

+1 (binding) On Fri, Feb 7, 2020, 12:43 AM Paul King wrote: > > Dear development community, > > I am happy to start the VOTE thread for a Groovy 3.0.0 release! > > This release includes 15 bug fixes/improvements as outlined in the > changelog: > >

Re: Welcome to our new committer : Eric Milles

Welcome Eric. On Sun, Aug 25, 2019, 8:34 PM Daniel.Sun wrote: > Hi all, > > I'd like to introduce you to Eric Milles, our new Apache Groovy committer! > Some of you may already know Eric for his work on Groovy Eclipse. He is a > very capable developer with the skills we need to help Groovy move

Re: Welcome Daniel Sun to Apache Groovy PMC

This is great news, welcome Daniel! On Mon, May 6, 2019 at 4:15 AM Paul King wrote: > > The Apache Groovy PMC has invited Daniel Sun to join the PMC and he has > accepted. You all probably know Daniel for his wonderful efforts on the > Parrot parser but he has been contributing in many other

Re: [VOTE] Release Apache Groovy 3.0.0-alpha-4

+1 (binding) On Thu, Dec 27, 2018 at 12:58 PM Paul King wrote: > > Dear development community, > > I am happy to start the VOTE thread for a Groovy 3.0.0-alpha-4 release! > This is expected to be the last "alpha" release for Groovy 3. > With 2019 upon us, it's time to put our focus on

Re: [VOTE] Release Apache Groovy 2.5.5

+1 (binding) On Thu, Dec 20, 2018 at 4:28 PM Paul King wrote: > > Dear development community, > > I am happy to start the VOTE thread for a Groovy 2.5.5 release! > > This release includes 20 bug fixes/improvements as outlined in the > changelog: > >

Re: [VOTE] Move the Groovy repositories on git-wip-us.apache.org to gitbox.apache.org

+1 On Sat, Dec 8, 2018, 1:54 PM Paul King As per DanielG's attached email, we need to move our remaining git-wip > repos: > Apache Groovy > Repository name:Description:Last changed:Links: > groovy.git Apache > Groovy < 2 days ago Summary

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

This can be caused by having GROOVY_HOME pointing to a different release, unsetting that environment variable or setting to the 2.5.3 directory should fix it. On Fri, Oct 12, 2018 at 1:05 AM Cédric Champeau wrote: > At this point, -1. See below. > > $ gpg --verify

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

+1 (binding) On Wed, Oct 10, 2018 at 10:55 PM Paul King wrote: > Dear development community, > > I am happy to start the VOTE thread for a Groovy 2.5.3 release! > > This release includes 52 bug fixes/improvements as outlined in the > changelog: > >

Re: [VOTE] Release Apache Groovy 2.5.3

On Linux I am having issues with the convenience binaries. The bin files seem to have CRLF line endings and fail to run. $ file ./groovy-2.5.2/bin/groovy ./groovy-2.5.2/bin/groovy: a /usr/bin/env sh script, ASCII text executable $ ./groovy-2.5.2/bin/groovy --version Groovy Version: 2.5.2 JVM:

Re: [VOTE] Release Apache Groovy 2.5.2

+1 (binding) On Fri, Aug 10, 2018 at 9:57 AM Paul King wrote: > Dear development community, > > I am happy to start the VOTE thread for a Groovy 2.5.2 release! > > This release includes 20 bug fixes/improvements as outlined in the > changelog: > >

Re: [VOTE] Release Apache Groovy 2.5.1

+1 (binding) On Tue, Jul 10, 2018 at 6:08 AM Paul King wrote: > > Dear development community, > > I am happy to start the VOTE thread for a Groovy 2.5.1 release! > > This release fixes some issues with OSGi, packaging issues related to JDK9+ > and some trait bugs that didn't make it in time for

Re: [VOTE] Release Apache Groovy 3.0.0-alpha-3

+1 (binding) On Fri, Jun 22, 2018 at 9:15 PM Paul King wrote: > > Dear development community, > > I am happy to start the VOTE thread for a Groovy 3.0.0-alpha-3 release! > This version is intended to be released at the same time as Groovy > 2.6.0-alpha-4 > and is the recommended next version of

Re: [VOTE] Release Apache Groovy 2.6.0-alpha-4

+1 (binding) On Fri, Jun 22, 2018 at 8:42 PM Paul King wrote: > > Dear development community, > > I am happy to start the VOTE thread for a Groovy 2.6.0-alpha-4 release! > > As per discussions on the user list, this is the last planned release for > the > GROOVY_2_6_X branch. This branch was

Re: Possible Problem

Looks like the problem is with the compound assignment using an attribute and not related to synchronized. I created issue GROOVY-8648 [1] for this problem. [1] https://issues.apache.org/jira/browse/GROOVY-8648 On Fri, Jun 15, 2018 at 6:59 AM Russel Winder wrote: > I have been tinkering a bit

Re: [VOTE] Release Apache Groovy 2.5.0

+1 (binding) On Sat, May 26, 2018 at 8:29 PM Paul King wrote: > > Dear development community, > > I am happy to start the VOTE thread for a Groovy 2.5.0 release! > > This release includes 12 bug fixes/improvements as outlined in the > changelog: > >

Re: [DISCUSS] Renumber Groovy 2.6 to 2.9

My opinion is that it should be left as 2.6. Since 2.6 has already undergone several pre-releases I think it will may be more confusing to re-number now. Renumbering may also give the impression that a 2.7 or 2.8 might be coming or at least make some wonder what happened to those versions. On

Re: [VOTE] Release Apache Groovy 2.5.0-rc-3

+1 (binding) On Sat, May 19, 2018 at 8:40 AM Paul King wrote: > > Dear development community, > > I am happy to start the VOTE thread for a Groovy 2.5.0-rc-3 release! > > This release includes 27 bug fixes/improvements as outlined in the > changelog: > >

Fwd: groovy git commit: GROOVY-5912: Static compilation: Groovy doesn't fail compilation when accessing package scope methods, but fails at runtime

Just a question, I thought that @TypeChecked is designed to work similar to dynamic mode as far as method dispatch and access (i.e., private/protected ok). If filtering methods by visibility is done in the `StaticTypeCheckingVisitor` wouldn't change that behavior. Is that something expected for

Re: CompilierConfiguration#CURRENT_JVM_VERSION

+1 for deprecating the current constant and new name (see note below). If the new constant wont be used internally then I might suggest no new constant is created. Else if it's created in order to provide an alternate to the deprecated one, would it make sense to provide it via

Re: FastStringUtils change

Definitely in favor of removing from 2_5_X, think it's a good idea. I doubt (though haven't benchmarked) that it really offers that much in terms of performance and memory savings and with JDK9 compat strings it doesn't work in it's currently form. Would it be worth considering leaving deprecated

Re: [VOTE] Support Java-like array

+1 Originally was going to vote 0, but had more time to devote to looking over the proposed PR/provisos and to consider the possible downsides. On Mon, May 7, 2018 at 12:21 PM, Paul King wrote: > I would like to see some more PMC votes for this proposal. > > On the one hand

Re: [VOTE] Release Apache Groovy 2.5.0-rc-2

+1 (binding) On Thu, May 3, 2018 at 1:49 AM, Paul King wrote: > > Dear development community, > > I am happy to start the VOTE thread for a Groovy 2.5.0-rc-2 release! > > This release includes 16 bug fixes/improvements as outlined in the > changelog: >

Re: [VOTE] Release Apache Groovy 3.0.0-alpha-2

+1 (binding) On Fri, Apr 13, 2018 at 8:20 AM, Daniel.Sun wrote: > Dear development community, > > I am happy to start the VOTE thread for a Groovy 3.0.0-alpha-2 release! > > This release includes 40 bug fixes/improvements as outlined in the > changelog: >

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

+1 (binding) On Thu, Apr 5, 2018, 9:14 AM Paul King wrote: > > Dear development community, > > I am happy to start the VOTE thread for a Groovy 2.5.0-rc-1 release! > > This release includes 18 bug fixes/improvements as outlined in the > changelog: > >

Re: [VOTE] Release Apache Groovy 2.4.15

+1 (binding) On Fri, Mar 23, 2018, 12:04 AM Paul King wrote: > > Dear development community, > > I am happy to start the VOTE thread for a Groovy 2.4.15 release! This is > mainly to fix a regression in calling static methods in interfaces. We were > trying to improve the

Re: [VOTE] Release Groovy 2.6.0-alpha-3

+1 (binding) On Fri, Mar 2, 2018 at 8:21 AM, Daniel.Sun wrote: > Dear development community, > > I am happy to start the VOTE thread for a Groovy 2.6.0-alpha-3 release! > > This release includes 18 bug fixes/improvements as outlined in the > changelog: >

Re: [VOTE] Release Apache Groovy 2.4.14

+1 (binding) On Sat, Feb 24, 2018 at 3:46 AM, Paul King wrote: > > Dear development community, > > I am happy to start the VOTE thread for a Groovy 2.4.14 release! > > This release includes 14 bug fixes/improvements as outlined in the > changelog: >

Re: [VOTE] Release Groovy 2.5.0-beta-3

+1 (binding) On Feb 19, 2018 9:36 PM, "Paul King" wrote: > > Dear development community, > > I am happy to start the VOTE thread for a Groovy 2.5.0-beta-3 release! > > There are still a few things we plan to work on before the final release > but > we anticipate this will be

Re: [VOTE] Release Apache Groovy 2.4.13 (take 3)

+1 On Nov 19, 2017 3:25 AM, "Paul King" wrote: > > Dear community, > > I am happy to start the VOTE thread for a Groovy 2.4.13 release! This > version fixes the problems reported with the previous candidate. > > This release includes 45 bug fixes/improvements as outlined in

Re: Removing our use of sun.misc.Unsafe

I would be in favor of removing Unsafe from the groovy-json subproject which I think is the only place where it's used. I had planned to propose this to the dev list but never got around to it. With compat strings in Java 9 I believe it will no longer be a viable optimization (at least not without

Re: [VOTE] Release Apache Groovy 2.5.0-beta-2

+1 (binding) On Sun, Oct 1, 2017 at 8:16 PM, Paul King wrote: > > Dear community, > > I am happy to start the VOTE thread for a Groovy 2.5.0-beta-2 release! > > This release includes 22 bug fixes/improvements as outlined in the > changelog: >

Re: [VOTE] [CANCELLED] Release Apache Groovy 2.6.0-alpha-1

I think rolling back to Gradle 3.5.1 for 2_6_X is a good idea. On Mon, Aug 28, 2017 at 4:07 PM, Paul King wrote: > I think one of the issues is that our build doesn't seem to play well with > Gradle 4+. Should we roll back to Gradle 3.5.1 for now? What do people > think? > >

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

+1 One thing I noticed that I don't think was mentioned so far is that the documentation from the sdk (doc/html/api) and docs (html/api/) archives looks to contain some Chinese text. On Sat, Aug 19, 2017 at 11:15 PM, Daniel Sun wrote: > Dear community, > > I am happy

Re: trySetAccessible for Java 9

Looks like the InjectedInvoker [1] is an implementation detail of the MH lookup, probably used to allow calling the caller sensitive method. I did not think that trySetAccessible prevents the message from appearing, so even using that new method wont get rid of the warning even with the default

Re: trySetAccessible for Java 9

The 2.4 branch still supports Java 6+ and believe that 2.5+ is where Java 7 starts as a baseline. The VMPlugin mechanism may be one approach to consider, having it provide a setAccessible(AccessibleObject) method where the Java7 or higher plugins can invoke the MethodHandle if available or fall

Re: [VOTE] Release Apache Groovy 2.4.12

+1 (binding) On Wed, Jun 21, 2017 at 3:15 AM, Paul King wrote: > > Dear community, > > I am happy to start the VOTE thread for a Groovy 2.4.12 release! > > This release includes 16 bug fixes/improvements as outlined in the > changelog: >

Re: using jdk9 specific API in the Groovy build

I like the idea of using a MethodHandle and it seems like a nice solution that wouldn't require building with Java 9. Though I imagine that there will probably be other changes that may require using the new module related classes that would require building with Java 9. On Sun, Jun 4, 2017 at

Re: Groovy 2.5.0-beta-1 release

+1 (binding) On Fri, Jun 2, 2017 at 7:33 AM, Jochen Theodorou wrote: > Dear community, > > I am happy to start the VOTE thread for a Groovy 2.5.0-beta-1 release! > > This release includes 8 bug fixes/improvements as outlined in the > changelog: >

Re: Indy vs default build

Does indy by default mean 1. only generate one set of groovy-* artifacts where any .groovy source files in the Groovy source itself are compiled using indy (no more separate indy jars) or 2. continue to have two sets of artifacts where the indy set would go in lib/ by default and -noindy jars

Re: Help with task: GroovyConsole improvement: configurable output area size

standard App | > Preferences menu > > > --emi > > On Sat, May 20, 2017 at 6:16 PM, John Wagenleitner < > john.wagenleit...@gmail.com> wrote: > >> Hi Emilian, >> >> On Sat, May 20, 2017 at 7:35 AM, Emilian Bold <emilian.b...@gmail.com> >> wrote: &

Re: Help with task: GroovyConsole improvement: configurable output area size

rt of the project. > > > --emi > > On Fri, May 19, 2017 at 6:01 PM, John Wagenleitner < > john.wagenleit...@gmail.com> wrote: > >> Hi Emilian, >> >> I added a comment on that issue, I think it would also be handy to have a >> new Preferences dialo

Re: Help with task: GroovyConsole improvement: configurable output area size

Hi Emilian, I added a comment on that issue, I think it would also be handy to have a new Preferences dialog for general settings such as this. Having a dialog behind a new menu item such as Edit > Preferences could have an edit box for inputting/displaying the output limit that is backed by a

Re: GROOVY-7979 and Index Overlay JSON parser behaviour

Hi James, My opinion is that it should fail to parse, similar to the following: import groovy.json.* def parser = new JsonSlurper().setType(JsonParserType.INDEX_OVERLAY) parser.parseText('{"num": 6-}') //groovy.json.JsonException: unexpected character - // //The current

Re: identifying low-hanging fruit tasks for the community

I think that's a great idea. The Contribute page [1] on groovy-lang.org currently links to the 'contrib' label for "..possible easy contributions that could get you started on your journey to become a Groovy committer." I used that link when I first started looking for ways to contribute. I

Re: [VOTE] Release Apache Groovy 2.4.11

ing > 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 using to test? >> >> On Wed, Apr 26, 2017 at 3:10 PM, John Wagenleitner < >> john.wagen

Re: [VOTE] Release Apache Groovy 2.4.11

0 (binding) I am finding that the fix [1] for GROOVY-8127 is causing a number of test failures [2] on the Grails master branch mostly related to the DirtyCheckable trait [3]. Same tests pass with 2.4.10. Lack of knowledge in this area so thus the neutral vote instead of -1. [1]

Re: creating final jar for testing changes made to groovy source code

On Fri, Apr 21, 2017 at 3:17 AM, Harish Dewan wrote: > Hi All, > To solve a probable problem, I forked and clone a git repo ( > https://github.com/apache/groovy.git ) for groovy and then used this > tutorial blog to import project in Intelj Idea ide ( >

Re: About the performance between master and GROOVY_2_5_X

Hi Daniel, Thanks, I had missed that. How do the tests under "subprojects/groovy-parser-antlr4/src/test" get run or are they not enabled on purpose? John On Thu, Apr 20, 2017 at 4:07 PM, 孙 岚 wrote: > Hi John, > > Parrot will be enabled for all projects: >

Re: About the performance between master and GROOVY_2_5_X

On Thu, Apr 20, 2017 at 9:11 AM, 孙 岚 wrote: > Hi all, > > I noticed that the performance of master is better than GROOVY_2_5_X. > > About *17% time saved* when running tests in the TeamCity CI > instance: > *master costs 18m:55s(TeamCity CI, Parrot disabled)*

Re: About code coverage of Groovy

I think if you run the 'check' task with -Pcoverage it'll generate the jacoco reports. On Tue, Apr 11, 2017 at 9:27 AM, Daniel Sun wrote: > Hi all, > > Where can I find the code coverage report of Groovy? If there is no > such thing currently, how about supporting

Re: build requirements for Groovy and language level in master

On Sat, Apr 8, 2017 at 1:11 AM, Jochen Theodorou wrote: > Hi all, > > so if we want to be serious about JDK9 support and not life with a > thousands of warnings displayed whenever you try to execute a Groovy > program or test (44k+ in our build for example)... then we will

Re: Trying to determine if a change in 2.4.8 was deliberate...

I created https://issues.apache.org/jira/browse/GROOVY-8140 for this and will remove the method. On Sat, Apr 1, 2017 at 2:14 PM, Jochen Theodorou <blackd...@gmx.org> wrote: > On 01.04.2017 20:04, John Wagenleitner wrote: > >> I remember looking at this and seeing that the comm

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

+1 On Wed, Mar 29, 2017 at 10:49 PM, Paul King wrote: > 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: >

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

+1 On Tue, Mar 14, 2017 at 8:05 AM, Paul King wrote: > 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

Re: [VOTE] Release Groovy 2.4.9

+1 On Feb 24, 2017 1:49 AM, "Paul King" wrote: 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?

Re: next releases

On Tue, Jan 17, 2017 at 1:55 AM, Daniel Sun wrote: > Hi Andres, > > > I'd suggest to release 2.5.0-beta and 3.0-ea together. Just like the JDK > > team has been posting JDK9 EA releases, we could do the same. We know for > > a fact we're going to break things, so let's

Re: [VOTE] Release Groovy 2.4.8

King <pa...@asert.com.au> wrote: > Can you check the version of gradle that is running? The artifacts are > built using install and install works fine for me from the src zip. > > On Tue, Jan 10, 2017 at 12:33 PM, John Wagenleitner > <john.wagenleit...@gmail.com> wro

Re: [VOTE] Release Groovy 2.4.8

When I run `gradlew install` from source (both from the downloaded zip and from the GROOVY_2_4_8 tag) I get the error below. Looks like prior to commit 9fa4b015e4a80ef03 [1] this was a warning but now it fails the build and wont install the artifacts in the local maven repo. [1]

Re: This was a surprise…

On Sun, Dec 18, 2016 at 6:42 AM, Russel Winder wrote: > (And Guillaume this is on Debian Sid using OpenJDK8 from the packaging, > but this is irrelevant to the problem… :-) > > BTW are all build recorded by Gradle Inc? > > > > |> ./gradlew clean > :buildSrc:compileJava

Re: Welcome to our new committer : Sergei Egorov

Welcome Sergei! On Sat, Dec 10, 2016 at 1:08 AM, Cédric Champeau wrote: > Hi folks, > > I'd like to introduce you to Sergei Egorov, our new Apache Groovy > committer! Some of you may already know Sergei for his work on macros, > which are going to make appearance in Apache

Re: "Parsing JSON is a mine field" <-- to read to improve Groovy's support

On Thu, Oct 27, 2016 at 1:25 AM, Guillaume Laforge wrote: > Hi there, > > I just saw this article yesterday: "Parsing JSON is a mine filed" > http://seriot.ch/parsing_json.html > > I haven't read it (yet) in details, but we might be able to improve > Groovy's JSON parsing

Re: making parser modules for antlr2 and antlr4

On Tue, Oct 25, 2016 at 1:53 PM, Jochen Theodorou wrote: > Hi, > > I am looking a bit into the usage of our old parser and keeping in mind > the new parser we want to eventually make the default. > > But one problem I talked about in the past already is the direct usage of >

Re: MethodClosure deserialization problem

On Sat, Oct 1, 2016 at 12:55 AM, Jochen Theodorou wrote: > hi all, > > as you guys may remember we added > > private Object readResolve() { >> if (ALLOW_RESOLVE) { >> return this; >> } >> throw new UnsupportedOperationException(); >> } >> > > to prevent proper

Re: uninformative gradle error messages

On Tue, Sep 27, 2016 at 11:15 AM, John Wagenleitner < john.wagenleit...@gmail.com> wrote: > On Mon, Sep 26, 2016 at 12:14 PM, Jochen Theodorou <blackd...@gmx.org> > wrote: > >> Hi all, >> >> maybe some people here with more gradle knowledge can help me a bi

Re: Recent commit breaks gradle builds

/apache/groovy/commit/82c9d20a160c7e4f59630f163a68df82f5e0eba4 > > 2016-09-19 1:49 GMT+02:00 John Wagenleitner <john.wagenleit...@gmail.com>: > >> A recent commit [1] to ClassInfo changed a private field from a Class to >> a WeakReference (to address memory leaks). In testing a project >> with

Re: Serious memory leak in groovy 2.4.7?

It might be related to GROOVY-7683 [1]. I ran the script with 2.4.8-SNAPSHOT and it completes successfully. I can replicate the problem with 2.4.7. As a workaround, I can get it to work with 2.4.7 if I use the following: groovy -Dgroovy.use.classvalue=true groovyOOM.groovy [1]

Re: uninformative gradle error messages

On Mon, Sep 26, 2016 at 12:14 PM, Jochen Theodorou wrote: > Hi all, > > maybe some people here with more gradle knowledge can help me a bit. I am > trying to run the jigsaw-136 build, of which I know gradle has problems > with, but well I am trying to work around those. So I

Fwd: Recent commit breaks gradle builds

-- Forwarded message -- From: Jochen Theodorou <blackd...@gmx.org> Date: Mon, Sep 19, 2016 at 12:12 AM Subject: Re: Recent commit breaks gradle builds To: dev@groovy.apache.org On 19.09.2016 01:49, John Wagenleitner wrote: > A recent commit [1] to ClassInfo changed

TeamCity CI builds broken

The jdk7 and 8 builds are failing. One commit I pushed yesterday (GROOVY-7683) timed out and since subsequent pushes are failing with the message: org.gradle.cache.internal.LockTimeoutException: Timeout waiting to lock Plugin Resolution Cache (/var/teamcity/.gradle/caches/3.0/plugin-resolution).

Re: Method resolution pondering

On Sat, Aug 27, 2016 at 4:22 AM, Jochen Theodorou 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 method resolution when >> multiple methods are matched. >> >>

Re: progress on executing tests with JDK9 status update

On Thu, Aug 25, 2016 at 7:57 AM, John Wagenleitner < john.wagenleit...@gmail.com> wrote: > > On Wed, Aug 24, 2016 at 10:29 PM, Jochen Theodorou <blackd...@gmx.org> > wrote: > >> On 25.08.2016 01:14, John Wagenleitner wrote: >> [...] >> >&g

Re: JDK 9 Jigsaw builds

; `-release` option of javac we can avoid `addmods` and the 1.9 target level > issue at the same time. > > > [1] > https://github.com/apache/groovy/commit/380ae614ae4d979f00e6e362d210e2dd1295bdce > > 2016-07-08 16:29 GMT+02:00 John Wagenleitner <john.wagenleit...@gma

Re: GroovyClassLoader deadlock in Groovy 2.4.6?

Having the full stack trace of one blocked thread and the blocking thread would help. Also, would be helpful to see how the template engine is used in code if possible. On Jun 20, 2016 7:48 PM, "lp_forum" wrote: Hi, I have a very simple single page app using Java 7 + Spring

Re: Improve Groovy class loading performance and memory management

On Tue, May 17, 2016 at 12:23 PM, Alain Stalder wrote: > [...] > > As I said, so far rather a hack, probably better to reimplement the > GroovyClassValuePreJava7 class instead? Performance under concurrent use? > Are other caches that apparently exist in ClassInfo also no issue

Re: Improve Groovy class loading performance and memory management

On Mon, May 16, 2016 at 11:56 PM, Jochen Theodorou wrote: > On 17.05.2016 07:53, Alain Stalder wrote: > >> That looks very good to me :) >> >> I will definitely try out the InvokerHelper.removeClass(clazz) with >> added ClassInfo removal plus

Re: Improve Groovy class loading performance and memory management

lled before collection. If so, from that I've seen that would still require some user intervention (java.beans.Introspector.flushFromCaches(clazz)) in order to clear the Introspector cache which keeps a Soft Reference to main method of a Script class which in turns references the Class. > &g

Re: Build from Git Master

This open issue looks like what I'm seeing. Though I haven't verified or tried the suggested workaround: https://github.com/asciidoctor/asciidoctor-gradle-plugin/issues/177 On Tuesday, February 23, 2016, Russel Winder <rus...@winder.org.uk> wrote: > On Tue, 2016-02-23 at 09:48 -0

Re: Build from Git Master

Yes that was my experience, the problems (added "Table of Contents" heading in some cells) I was seeing in tables was not just with 1.5.3 and jdk9 but also jdk7/8. That's why I didn't go ahead with bumping the version in master. On Tue, Feb 23, 2016 at 2:51 AM, Russel Winder

Re: Build from Git Master

Looks like the problem is fixed in asciidoctor-gradle-plugin:1.5.3 (master currently using 1.5.2). I tested 1.5.3 and it works with the latest jdk9 snapshot release (ea+106), but it seems to add some odd headings in tables. Haven't had time to look into it. On Feb 22, 2016 4:12 AM, "Russel

Re: Preparing for a release

ng this >> one. >> >> Other opinions? >> >> Cheers, Paul. >> >> >> On Wed, Feb 17, 2016 at 6:02 AM, John Wagenleitner >> <john.wagenleit...@gmail.com> wrote: >> >>> Hi Jim, >>> >>> I think the f

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

roper synchronization and initializaton of anything that is visible across > threads, so no external synchronization is required. > > what do you guys think? > > bye Jochen > > Am 06.01.2016 um 00:27 schrieb John Wagenleitner: > >> My mistake, I didn't know there w

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

Not sure but wonder if HandleMetaClass#myMetaClass was static to avoid having to perform a lookup for each HMC instance. Probably not a issue but thought I'd bring attention to it. On Tue, Jan 5, 2016 at 10:13 AM, wrote: > Repository: groovy > Updated Branches: >

Github pull requests not picked up by CI server

The builds.apache.org CI server doesn't seem to be picking up Github pull requests. If there's a more appropriate way to report this kind of issue please let me know and I'll follow it in the future.