next generation CliBuilder?

Would there be any interest in a next generation CliBuilder that is based on [picocli][1] instead of commons-cli? This would enable new features like: * support for nested [subcommands][2] * strongly typed [positional parameters][3] * command line [autocompletion][4] * [ANSI colors][5] in usage he

Re: next generation CliBuilder?

;> to integrate it into Groovy sounds good to me... ||-) >>> >>> Does anyone knows of any shortcomings of picocli or miss some CLI >>> features in the library ? Or are there any other (long running) plans to >>> replace the existing CliBuilder implementat

Re: next generation CliBuilder?

tribute to @Unparsed at our leisure in a backward compatible way. > > What do you think? > > Paul. > > > On Wed, Mar 21, 2018 at 2:38 PM, Remko Popma > wrote: > >> >> On Wed, Mar 21, 2018 at 12:43 Paul King wrote: >> >>> On Wed, Mar 21, 2018 a

Re: next generation CliBuilder?

On Wed, Mar 21, 2018 at 5:23 PM, Jochen Theodorou wrote: > > > Am 21.03.2018 um 02:11 schrieb Paul King: > >> Picocli has always looked like a nice alternative. It wasn't an option >> for me before it had the api but picocli 3 seems to have that covered. >> > > can you refresh my memory about the

Feedback on groovy.cli.Option annotation

The groovy.cli.Option annotation currently has three attributes for modeling the number of arguments (arity) of an option: - boolean optionalArg() default false - int numberOfArguments() default 1 - String numberOfArgumentsString() default "" Are we open to changing this to a single at

Re: Feedback on groovy.cli.Option annotation

oking extremely unwieldy, then the 2.5 release would be an > appropriate streamlining point. > > Cheers, Paul. > > > On Sat, Mar 24, 2018 at 11:46 AM, Remko Popma > wrote: > >> The groovy.cli.Option annotation currently has three attributes for >

picocli-based CliBuilder backwards compatibility

CliBuilder exposed some commons-cli classes (see below). Is it okay to remove these, or should these be left as deprecated properties in the CliBuilder class to retain binary compatibility with pre-2.5 versions? Note that if these properties remain the new picocli-based implementation will ignore

Re: picocli-based CliBuilder backwards compatibility

the legacy > version. The goal should be to have commons-cli being a dependency of only > that module. > > Cheers, Paul. > > On Sun, Mar 25, 2018 at 1:58 PM, Remko Popma > wrote: > >> CliBuilder exposed some commons-cli classes (see below). >> >> Is it o

Re: picocli-based CliBuilder backwards compatibility

you want. > > Paul. > > >> On Sun, Mar 25, 2018 at 8:55 PM, Remko Popma wrote: >> Thanks, it makes things easier if these properties can be changed. >> >> FYI, the following classes also use commons-cli directly, not sure which are >&g

Re: About creating instances of non-static inner classes with Java-Like syntax

Eric, Yes this is used. For example, picocli has an Ansi enum (ON, OFF, AUTO), with a nested inner class Text. A Text instance is created with `currentAnsi.new Text(“@|bold hello|@“);` The outer class determines whether Ansi escape codes are emitted when the text is rendered. I’m sure it’

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

+1 On Thu, May 3, 2018 at 6:52 PM, John Wagenleitner < john.wagenleit...@gmail.com> wrote: > +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 include

Re: Groovy 2.5.0-rc-2 breaks Gant

In 2.5.0-rc-2, groovy.util.CliBuilder delegates to groovy.cli.picocli.CliBuilder. The error is that the `parser` property of this class is no longer writable. You can resolve this with 2.5.0-rc-2 by either not setting the `parser` property in the CliBuilder constructor or using the groovy.cli.comm

Re: Groovy 2.5.0-rc-2 breaks Gant

I think I found a way to fix this. See https://github.com/apache/groovy/pull/696 This PR adds CliBuilder.setParser and CliBuilder.setFormatter methods that ignore the specified value and print a warning to stderr. On Sun, May 6, 2018 at 9:14 PM, Remko Popma wrote: > In 2.5.0-r

Re: Groovy 2.5.0-rc-2 breaks Gant

> Cheers, Paul. > > > On Mon, May 7, 2018 at 3:45 PM, Keegan Witt wrote: > >> I'll take a look. I'll also see if there are other places that can break. >> >> If there are several ways it can break, then maybe we should not use a >> delegate to pic

Re: Groovy 2.5.0-rc-2 breaks Gant

the game compared to what we'd like. I'd really like to get +ve feedback >> from a SNAPSHOT with that change before doing another release including it. >> I can merge in a couple of days time after conference commitments. >> >> Cheers, Paul. >> >> On

Re: What the... static compile by default

Over at Log4j we just decided to migrate from git-wip-us to gitbox . Using gitbox will allow our projects to integrate better with GitHub > including the

Re: What the... static compile by default

https://gitbox.apache.org/setup/ On Sat, May 12, 2018 at 12:59 AM, Mario Garcia wrote: > Remko Could you add a link to Gitbox ? > > El vie., 11 may. 2018 a las 17:52, Remko Popma () > escribió: > >> Over at Log4j we just decided to migrate from git-wip-us to g

Re: [VOTE] Support Java-like array

Why? I count three +1 and one +0 votes. Remko > On May 13, 2018, at 2:21, Daniel.Sun wrote: > > Hi Paul, > > The relevant JIRA ticket has been closed as the GEP fails to get three > +1 from PMC members. > > P.S. I seldom use arrays directly but for performance. > > Cheers, > Daniel.Sun

Re: [VOTE] Support Java-like array

Didn’t see a requirement for three +1 votes anywhere... Paul asked for “I would like to see some more PMC votes for this proposal.” Since then, two PMC members voted, one +1 and one +0. Seems sufficient to me... Am I wrong? PMC members, if you feel differently, could you please add your vote? R

Re: [VOTE] Support Java-like array

That’s probably why over at Log4j we use slightly different language for voting: “The vote will remain open for 72 hours (or more if required). At least 3 +1 votes ...” It seems unfair that by not participating, it is possible to essentially vote -0 or -1 without justification... Thoughts? Re

Re: [VOTE] Support Java-like array

milar to [VOTE][LAZY]. > 72 hours is the minimum for such votes but there is no maximum time delay > - though waiting too long isn't a good idea since the circumstances which > lead to earlier +1s might have changed. > > If anyone has improvements for this wording, let me kn

Re: [VOTE] Support Java-like array

t; you don't have at least one) but can be vetoed with a single -1 binding vote >>> A committer creating a PR request is similar to [VOTE][LAZY]. >>> 72 hours is the minimum for such votes but there is no maximum time delay - >>> though waiting too long isn't a go

Groovy 2.5 CliBuilder article (request for feedback)

Hi everyone, I finished a first draft of an article on Groovy 2.5 CliBuilder (https://github.com/remkop/picocli/wiki/Groovy-2.5-CliBuilder-Renewal). I plan to publish this on DZone and Java Code Geeks when complete. I'd appreciate your feedback and suggestions for improvement! Remko

Re: CompilierConfiguration#CURRENT_JVM_VERSION

+1 On Tue, May 15, 2018 at 7:01 PM, Paul King wrote: > > Hi all, > > In CompilerConfiguration we have a public constant CURRENT_JVM_VERSION > which actually represents the minimum JDK version supported by a particular > version of Groovy (potentially on a particular VM runtime). I was thinking >

Re: 2.5.0-rc-3

Where do the release notes live? I can’t find them on GitHub. Remko > On May 18, 2018, at 20:20, Paul King wrote: > > > Last call for changes in rc-3. I hope to prepare the candidate for voting > tomorrow. > > If all goes well, please then consider the 2_5_X branch semi-frozen. We still

Re: Groovy 2.5.0-rc-2 breaks Gant

? Remko > On May 18, 2018, at 22:14, Keegan Witt wrote: > > So do you want to change this back for RC3? I know it's late to change this, > but arguably it was late to change it in RC2 too. > > -Keegan > > >> On Thu, May 10, 2018, 11:08 AM Remko Popma wro

Re: 2.5.0-rc-3

Thanks Daniel! > On May 18, 2018, at 22:00, Daniel.Sun wrote: > > FYI > https://github.com/groovy/groovy-website/blob/master/site/src/site/releasenotes/groovy-2.5.adoc > > http://groovy-lang.org/releasenotes/groovy-2.5.html > > Cheers, > Daniel.Sun > > > > > > > -- > Sent from: http://g

Re: [DISCUSS] Renumber Groovy 2.6 to 2.9

Is there a web page somewhere that explains the vision (so to speak) of what features will go into 3.0 and what will go in the version preceding it? Or is it roughly the same content but targeting different Java versions? Remko > On May 20, 2018, at 12:58, Paul King wrote: > > > Hi, > > I

Re: [DISCUSS] Renumber Groovy 2.6 to 2.9

+1 Makes sense. Remko > On May 20, 2018, at 19:35, Daniel.Sun wrote: > > Hi Paul, > > +1 > As the main version before 3.0.0 is 2.6 currently, I think renumbering > 2.6 to 2.9 can reflect the changes in 2.6 better. > > Cheers, > Daniel.Sun > > > > > -- > Sent from: http://groovy.3

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

> On May 21, 2018, at 13:35, Daniel.Sun wrote: > > My pleasure :-) > > P.S. You've collected more than three +1 from PMC members. Still probably good to keep the vote open for the announced 72 hours in case someone finds a showstopper. Remko > > Cheers, > Daniel.Sun > > > > -- > Sent f

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

+1 When building the GROOVY_2_5_X branch, I see failing RAT tests: $project/subprojects/groovy-templates/out/test/resources/inc ludes/hello-escaped.txt $project/subprojects/groovy-templates/out/test/resources/includes/hello.html $project/subprojects/groovy-templates/out/test/resources/raw.txt $pr

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

ve still > worked but not achieved the desired outcome. > > We'll have to check all of the doco. There are numerous adoc files for > tools-groovy, tools-groovyc, groovydoc, etc. > > Cheers, Paul. > > > On Tue, May 22, 2018 at 12:04 AM, Remko Popma > wrote: >

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

this on Java 8 though... Remko > On May 22, 2018, at 11:52, Paul King wrote: > > > Sorry, I accidentally went off-list. > > -- Forwarded message -- > From: Paul King > Date: Tue, May 22, 2018 at 12:22 PM > Subject: Re: [VOTE] Release Apache Groovy 2

Re: Groovy 2.5.0-rc-3 fails to break Gant [was Groovy 2.5.0-rc-2 breaks Gant]

Glad to hear that. Remko On Wed, May 23, 2018 at 1:55 Russel Winder wrote: > Hi, > > All Gant master/HEAD tests pass with Groovy 2.5.0-rc-3. > > :-) > > -- > Russel. > == > Dr Russel Winder t: +44 20 7585 2200 > 41 Buckmaster Roadm: +44 7770 465 0

Re: [VOTE] Release Apache Groovy 2.5.0

+1 Looks good from what I've tried. On Mon, May 28, 2018 at 5:51 AM, John Wagenleitner < john.wagenleit...@gmail.com> wrote: > +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 rele

Re: Groovy 2.5 CliBuilder article (request for feedback)

All, I polished the Groovy 2.5 CliBuilder article some more (https://github.com/remkop/picocli/wiki/Groovy-2.5-CliBuilder-Renewal ). Feedback (positive or negative) would be great. On Tue, May 15, 2018 at 11:40 PM, Remko Popma wrote: > Hi everyone, > > I finished a first draft of a

Re: Commons cli contribution?

Personally, I would invite everyone using Commons CLI to migrate to picocli . But I may be biased... :-) Remko On Tue, May 29, 2018 at 2:06 AM, Romain Manni-Bucau wrote: > Hi guys > > Saw you added some annotations to write a cli in groovy cli, did you try > (

Re: Groovy 2.5 CliBuilder article (request for feedback)

the joke ;-) > > 2) I'd use // 1, // 2, // 3 for pointing out individual lines in the > examples. That way, you can still copy+paste them. > > -Jesper > >> On 28 May 2018, at 19.03, Remko Popma wrote: >> >> All, >> >> I polished the Groovy

Re: Groovy 2.5 CliBuilder article (request for feedback)

han > "annotating fields or setter methods" > > Cheers, Paul. > > >> On Tue, May 29, 2018 at 3:03 AM, Remko Popma wrote: >> All, >> >> I polished the Groovy 2.5 CliBuilder article some more >> (https://github.com/remkop/picocli/wiki/Groov

Re: Groovy 2.5 CliBuilder article (request for feedback)

y 29, 2018 at 9:43 AM, Remko Popma wrote: >> Paul, >> >> I’ll change “annotating properties” to “annotating fields”. > > I was suggesting the other way around. Field-like declarations in Groovy > without an explicit visibility modifier are properties. That's what y

Re: Commons cli contribution?

li dev list before: >>>> >>>> https://markmail.org/message/45jgonianj4sw7i4 >>>> >>>> You can probably use it all directly from Java apart from the >>>> Closure-based converters (which are also possible from Java just a big >>>> uglie

Re: Commons cli contribution?

(Adding Romain to recipients) On Tue, May 29, 2018 at 13:48 Remko Popma wrote: > Romain, > > I’m hoping for picocli to become the successor to Commons CLI (and to some > extent JCommander, args4j, jopt-simple etc). > > Please take a look at the project. (Nutshell: apps can

Re: Commons cli contribution?

n have injection support). > > Cli provides a strong parsing bit misses a user friendly api so Im just > trying to make it converging + Id like to see it hosted @asf to reuse it in > other asf projects without more careness. > > > Le mar. 29 mai 2018 06:52, Remko Popma a écrit : &

Re: Groovy 2.5 CliBuilder article (request for feedback)

Cool! Thanks again! Remko > On May 29, 2018, at 14:26, Paul King wrote: > > LGTM! > >> On Tue, May 29, 2018 at 2:17 PM, Remko Popma wrote: >> Thanks for the clarification. I’ve made some changes based on your feedback. >> >> Please let me know if you spo

Re: Groovy 2.5 CliBuilder article (request for feedback)

me a date and time? Cheers, Remko On Tue, May 29, 2018 at 15:34 Remko Popma wrote: > Cool! > Thanks again! > > > Remko > > On May 29, 2018, at 14:26, Paul King wrote: > > LGTM! > > On Tue, May 29, 2018 at 2:17 PM, Remko Popma > wrote: > >> Thanks

Re: Troubles with IDEA setup

I cannot reproduce this problem on my Windows 10 laptop... On Wed, May 30, 2018 at 8:43 Jochen Theodorou wrote: > > > Am 23.05.2018 um 13:33 schrieb Cédric Champeau: > > Thanks for checking, Marcin. For reference, stub generation takes long > > but passes. It's really the semantic analysis whic

Re: [ANNOUNCE] Apache Groovy 2.5.0 released

Is anyone planning to blog this announcement on http://blogs.apache.org ? > On May 30, 2018, at 16:47, Guillaume Laforge wrote: > > Woohoo, congrats everyone! > >> On Wed, May 30, 2018 at 9:15 AM Graeme Rocher >> wrote: >> Awesome! Congrats all! >> >> — >> Graeme Rocher >> >>> On 30 May

Re: [ANNOUNCE] Apache Groovy 2.5.0 released

I’m guessing everyone is busy with gr8conf. Any objections if I blog this announcement on http://blogs.apache.org ? I’ll just repeat the text of the announcement mail that Paul sent out. Let me know if I can go ahead. On Wed, May 30, 2018 at 17:39 Remko Popma wrote: > Is anyone planning

Re: [ANNOUNCE] Apache Groovy 2.5.0 released

Done. https://blogs.apache.org/logging/entry/announce-apache-groovy-2-5 On Wed, May 30, 2018 at 8:27 PM, Paul King wrote: > Please do. Thanks. > > On Wed., 30 May 2018, 11:44 am Remko Popma, wrote: > >> I’m guessing everyone is busy with gr8conf. >> Any o

Re: [ANNOUNCE] Apache Groovy 2.5.0 released

I posted to General but my blog posts seem to end up under Apache Logging Services. Looks a bit weird. Apologies. On Wed, May 30, 2018 at 8:31 PM, Remko Popma wrote: > Done. > > https://blogs.apache.org/logging/entry/announce-apache-groovy-2-5 > > > > On Wed, May 30, 2018

Groovy project blog at blogs.apache.org

I propose we get a Groovy project blog at blogs.apache.org. This is a good place to announce new releases or have content articles and let the ASF help expose it to a wider audience. If there’s interest, the PMC needs to request this to get things started. See http://www.apache.org/dev/project-b

Re: Groovy project blog at blogs.apache.org

Great! Please grant me (blog user “rpopma”) access rights when the blog is created. On Tue, Jul 10, 2018 at 11:25 Paul King wrote: > Good idea. I put in a request: > > https://issues.apache.org/jira/browse/INFRA-16744 > > Paul. > > On Tue, Jul 10, 2018 at 11:56 AM Remko P

Re: Groovy project blog at blogs.apache.org

gt; > Cheers, Paul. > > > On Tue, Jul 10, 2018 at 2:48 PM Remko Popma wrote: > >> Great! >> >> Please grant me (blog user “rpopma”) access rights when the blog is >> created. >> >> On Tue, Jul 10, 2018 at 11:25 Paul King wrote: >> >>>

Re: [ANN] Announcing CodeNarc 1.2

Blogged: https://blogs.apache.org/groovy/entry/announce-announcing-codenarc-1-2 On Tue, Jul 10, 2018 at 3:46 AM, wrote: > The *CodeNarc** Team *is proud to announce the release of version *1.**2*. > > *CodeNarc* is a static analysis tool for Groovy > source code. > > Vers

Re: [VOTE] Release Apache Groovy 2.5.1

+1 > On Jul 10, 2018, at 22:07, 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 2.5.0.

Re: [ANNOUNCE] Apache Groovy 2.5.1 released

Blogged: https://blogs.apache.org/groovy/entry/groovy-2-5-1-released Please share on social media. On Fri, Jul 13, 2018 at 11:12 PM, Paul King wrote: > Dear community, > > The Apache Groovy team is pleased to announce version 2.5.1 of Apache > Groovy. > Apache Groovy is a multi-faceted programm

Re: preparing for release 2.5.2

If you can wait 30 minutes I’ll update the picocli dependency to the latest version. Now running the tests. (Shameless plug) Every java main() method deserves http://picocli.info > On Aug 9, 2018, at 16:37, Paul King wrote: > > > I am just about ready to proceed with getting a candidate 2.5.

Re: preparing for release 2.5.2

Done with the dependency upgrade. Sorry it took a bit longer than expected. (Shameless plug) Every java main() method deserves http://picocli.info > On Aug 9, 2018, at 17:30, Remko Popma wrote: > > If you can wait 30 minutes I’ll update the picocli dependency to the latest >

Re: [ANNOUNCE] Apache Groovy 2.5.2 Relased

Blogged: https://blogs.apache.org/groovy/entry/groovy-2-5-2-released Please share on social media! On Tue, Aug 14, 2018 at 4:31 PM, Paul King wrote: > Dear community, > > The Apache Groovy team is pleased to announce version 2.5.2 of Apache > Groovy. > Apache Groovy is a multi-facet programming

Re: [Bug] [2.5.2] groovy.cli.picocli.CliBuilder.parseFromSpec does not cast its result to the correct type

Kevin, that’s strange, there are working unit tests that do exactly the same... For example: https://github.com/apache/groovy/blob/GROOVY_2_5_X/subprojects/groovy-cli-picocli/src/test/groovy/groovy/cli/picocli/CliBuilderTest.groovy#L794 On Wed, Sep 12, 2018 at 12:52 Kevin Perkins wrote: > Hell

Re: [Bug] [2.5.2] groovy.cli.picocli.CliBuilder.parseFromSpec does not cast its result to the correct type

something particular to CliBuilder.) Remko (Shameless plug) Every java main() method deserves http://picocli.info > On Sep 12, 2018, at 13:40, Remko Popma wrote: > > Kevin, that’s strange, there are working unit tests that do exactly the > same... > For example: > &g

Re: upcoming Groovy 2.5.3 release

Thanks for the heads up. Planning to bump picocli to 3.6 (adding internationalization support, @Command methods, IDefaultValueProvider interface, better error messages and bash completion script improvements). The internationalization may be good to bring into the CliBuilder API. (But not sure I

Re: upcoming Groovy 2.5.3 release

ing wrote: > > Those sound like great additions but I don't want to wait too long since some > of the fixes are important to get out soon. We'll no doubt have a 2.5.4 in > another month for anything you don't get done. > > Cheers, Paul. > > > >>

2.5.x build error

Is anyone seeing this error when building the 2.5.x branch? java.lang.BootstrapMethodError: call site initialization exception at com.github.spotbugs.SpotBugsPlugin.lambda$configureForSourceSet$7(SpotBugsPlugin.java:199) at org.gradle.util.GUtil.uncheckedCall(GUtil.java:459)

Re: 2.5.x build error

;>> I don't normally run the quality checks but I see it in the CI server: >>> >>> http://ci.groovy-lang.org/viewType.html?buildTypeId=Groovy_CoverageIndyRuntime >>> >>> Perhaps the version of spotbugs vs gradle on the 2_5_X branch

Re: Groovy 2.5.3-SNAPSHOT join build error

One of the changes in 2.5.3 is a picocli upgrade. A potentially breaking change is that error messages for things like missing required options have been improved in picocli-3.6. If Nextflow uses picocli, and the tests verify the error message text, this may cause tests to fail. On Mon, Sep 17, 20

Re: About simplifying the switch for runtime groovydoc

MG’s arguments make sense to me. Remko > On Oct 21, 2018, at 23:05, MG wrote: > > Yea, sure. But doesn't a new shorthand syntax always have that trait ?-) > And would that not mean that we can never, ever again introduce a shorthand > notation in Groovy for anything, unless it is syntacticall

Re: About simplifying the switch for runtime groovydoc

I like the short notation much better than the long notation. The /** notation for Javadoc was cryptic 20 years ago but there was no resistance to the idea. Why not? Because it was such a useful feature of the language! I think we all agree that making GroovyDoc available at runtime is a use

Re: About simplifying the switch for runtime groovydoc

> On Oct 25, 2018, at 21:48, Keith Suderman wrote: > > > >> On Oct 24, 2018, at 8:31 PM, Remko Popma wrote: >> >> In addition, there is nothing about the long @GroovyDoc notation that tells >> me the doc string is retained at runtime. So it isn’t ac

Re: About simplifying the switch for runtime groovydoc

Daniel, Question: how do I consume the groovydoc string at runtime in the application? For example, I would like to do something like this: —— /**@ * Encrypts a file. */ class Encrypt { static void main(String... args) { def cli = new CliBuilder() def descr = // how to get

Re: groovy.apache.org website/repo

The Log4j PCM is thinking to move to gitbox. Any tips, or snags/pitfalls to be aware of? Remko. (Shameless plug) Every java main() method deserves http://picocli.info > On Nov 8, 2018, at 17:45, Daniel Sun wrote: > > Nice work :) > > Cheers, > Daniel.Sun > > > > > -- > Sent from: http:/

Re: [VOTE] Release Apache Groovy 2.5.4

+1 Remko. (Shameless plug) Every java main() method deserves http://picocli.info > On Nov 9, 2018, at 19:10, Guillaume Laforge wrote: > > +1 (binding) > > Looking good > >> On Fri, Nov 9, 2018 at 10:56 AM Andres Almiray wrote: >> +1 (binding) >> >> Built from source. >> No obvious problems

Re: [ANNOUNCE] Apache Groovy 2.5.4 released

Blogged: https://blogs.apache.org/groovy/entry/groovy-2-5-4-released Please share on social media. On Monday, November 12, 2018, Paul King wrote: > Dear community, > > The Apache Groovy team is pleased to announce version 2.5.4 of Apache > Groovy. > Apache Groovy is a multi-faceted programming

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

+1 On Sun, Dec 9, 2018 at 6:54 AM Paul King wrote: > 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 a

Re: [ANNOUNCE] Apache Groovy 2.4.16 released

Blogged: https://blogs.apache.org/groovy/entry/groovy-2-4-16-released On Thu, Dec 13, 2018 at 7:17 PM Paul King wrote: > Dear community, > > The Apache Groovy team is pleased to announce version 2.4.16 of Apache > Groovy. > Apache Groovy is a multi-faceted programming language for the JVM. > Fu

Re: [VOTE] Release Apache Groovy 2.5.5

+1 > On Dec 22, 2018, at 23:37, Andres Almiray wrote: > > +1 > > Build successful on OSX. No errors. > > --- > Java Champion; Groovy Enthusiast > JCP EC Associate Seat > http://andresalmiray.com > http://www.linkedin.com/in/aalmiray > -- > What goes up

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

+1 > On Dec 29, 2018, at 10:39, John Wagenleitner > wrote: > > +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" rel

Re: [ANNOUNCE] Apache Groovy 3.0.0-alpha-4 released

Blogged: https://blogs.apache.org/groovy/entry/groovy-3-0-0-alpha Please share on social media. On Mon, Dec 31, 2018 at 7:46 PM Daniel.Sun wrote: > groovy this year, groovier next year ;-) > > > > > > - > Apache Groovy committer > Blog: http://blog.sunlan.me > Twitter: @daniel_sun > > -- > S

Re: About the lazy consensus on Pull Requests

No objection from me, assuming that major changes are brought up on the mailing list first. Remko > On Jan 27, 2019, at 3:09, Daniel.Sun wrote: > > Hi all, > > In order to make all major changes reviewed, I create PRs for each > major change. And the PRs will be merged in 72 hours by

Re: [VOTE] Release Apache Groovy 2.5.6

+1 Remko. > On Feb 4, 2019, at 7:31, John Wagenleitner > wrote: > > +1 (binding) > >> On Fri, Feb 1, 2019 at 3:04 AM Paul King wrote: >> >> Dear development community, >> >> I am happy to start the VOTE thread for a Groovy 2.5.6 release! >> >> This release includes 24 bug fixes/improvemen

Re: [ANNOUNCE] Apache Groovy 2.5.6 released

Thank for doing the release, Paul! Blogged: https://blogs.apache.org/groovy/entry/groovy-2-5-6-released On Mon, Feb 4, 2019 at 10:56 PM Daniel.Sun wrote: > Nice work, Paul. > > Cheers, > Daniel.Sun > > > > - > Apache Groovy committer > Blog: http://blog.sunlan.me > Twitter: @daniel_sun > >

Re: Welcome Daniel Sun to Apache Groovy PMC

Congrats, Daniel! Remko > On May 6, 2019, at 21:35, Daniel.Sun wrote: > > Thanks for your kind words :-) > I believe Groovy will be groovier and groovier because of our endless > efforts. > > Cheers, > Daniel.Sun > > > > > - > Apache Groovy committer > Blog: http://blog.sunlan.me >

CliBuilder improvements

The vote thread for 3.0.0-beta-1 woke me up. :-) Is there still a chance to include enhancements to CliBuilder in 3.0, or does the beta mean no new features? (And are there any rough timelines for 3.0 GA?) I was thinking about the following features: * indexed and typed positional parameters (cur

Re: [ANNOUNCE] Apache Groovy 2.5.7 Released

Blogged: https://blogs.apache.org/groovy/entry/groovy-2-5-7-released On Sat, May 11, 2019 at 12:58 AM Daniel.Sun wrote: > Nice work, Paul :-) > > Cheers, > Daniel.Sun > > > > > - > Apache Groovy committer & PMC member > Blog: http://blog.sunlan.me > Twitter: @daniel_sun > > -- > Sent from:

Re: [ANNOUNCE] Apache Groovy 2.4.17 Released

Blogged: https://blogs.apache.org/groovy/entry/groovy-2-4-17-released On Sat, May 11, 2019 at 12:48 AM Daniel.Sun wrote: > Nice work, Paul :-) > > Cheers, > Daniel.Sun > > > > > - > Apache Groovy committer & PMC member > Blog: http://blog.sunlan.me > Twitter: @daniel_sun > > -- > Sent from:

Re: [ANNOUNCE] Apache Groovy 3.0.0-beta-1 Released

Blogged: https://blogs.apache.org/groovy/entry/groovy-3-0-0-beta On Sun, May 12, 2019 at 7:53 AM Paul King wrote: > Eric, when trying to build? > > On Sun, May 12, 2019 at 5:54 AM Milles, Eric (TR Tech, Content & Ops) < > eric.mil...@thomsonreuters.com> wrote: > >> I am getting the following er

requesting your advice on picocli modules

Hi, I maintain the picocli library for creating command line applications in Groovy, Java, and other JVM languages. I have a question for the Groovy community (both users and developers): Currently, the picocli main jar contains both the core `picocli` package and a `picocli.groovy` package with

Re: requesting your advice on picocli modules

nt:* Thursday, May 30, 2019 3:05 PM > *To:* us...@groovy.apache.org > *Cc:* dev@groovy.apache.org > *Subject:* Re: requesting your advice on picocli modules > > + 1 picoli-groovy.jar > > Great project BTW! > > El jue., 30 may. 2019 a las 14:51, Remko Popma () > es

Re: requesting your advice on picocli modules

> Hi Remko, > > I agree option 1) is the cleanest, as well as it being the direction all > of Groovy seems to be moving. > > Cheers, > mg > > > On 30/05/2019 14:50, Remko Popma wrote: > > Hi, > > I maintain the picocli library for creating command line

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

+1 On Mon, Jul 8, 2019 at 2:27 AM Daniel.Sun wrote: > Dear development community, > > I am happy to start the VOTE thread for a Groovy 3.0.0-beta-2 release! > > This release includes 40 bug fixes/improvements as outlined in the > changelog: > > https://issues.apache.org/jira/secure/ReleaseNote.j

Re: [ANNOUNCE] Apache Groovy 3.0.0-beta-2 Released

Blogged: https://blogs.apache.org/groovy/entry/groovy-3-0-0-beta1 On Mon, Jul 15, 2019 at 1:22 AM Guillaume Laforge wrote: > Congrats on this release! > > Le dim. 14 juil. 2019 à 12:57, 孙 岚 a écrit : > >> Dear community, >> >> The Apache Groovy team is pleased to announce version 3.0.0-beta-2 o

Re: [ANNOUNCE] Apache Groovy 3.0.0-beta-2 Released

link URL contains beta-ONE instead of TWO :-) > > On Mon, Jul 15, 2019 at 12:33 PM Remko Popma > wrote: > >> Blogged: >> https://blogs.apache.org/groovy/entry/groovy-3-0-0-beta1 >> >> On Mon, Jul 15, 2019 at 1:22 AM Guillaume Laforge >> wrote: >> >>>

Re: [groovy] branch master updated: GROOVY-9222: Bump picocli to 4.0.2

Darn, you’re fast, Daniel! :-) > On Aug 12, 2019, at 19:18, sun...@apache.org wrote: > > This is an automated email from the ASF dual-hosted git repository. > > sunlan pushed a commit to branch master > in repository https://gitbox.apache.org/repos/asf/groovy.git > > > The following commit(s

Re: Welcome to our new committer : Eric Milles

Welcome, Eric! Remko. > On Aug 26, 2019, at 16:27, Mauro Molinari wrote: > > Great news, congratulations Eric! > > Mauro > > Il 26/08/2019 05:37, Daniel.Sun ha scritto: >> Hi all, >> >> I'd like to introduce you to Eric Milles, our new Apache Groovy committer! >> Some of you may already kn

Re: Field order from traits

On Mon, Dec 2, 2019 at 9:31 Milles, Eric (TR Tech, Content & Ops) < eric.mil...@thomsonreuters.com> wrote: > Trait fields for properties are added by TraitComposer as it encounters > the getter methods (around line 250). Methods are processed in the order > returned from ClassNode#getDeclaredMeth

Re: [ANNOUNCE] Apache Groovy 3.0.0-rc-2 released

Nice work, Paul! Remko. > On Dec 9, 2019, at 3:30, Paul King wrote: > > Dear community, > > The Apache Groovy team is pleased to announce version 3.0.0-rc-2 of > Apache Groovy. > Apache Groovy is a multi-faceted programming language for the JVM. > Further details can be found at the https:/

Re: [VOTE] Release Apache Groovy 2.4.18

+1 On Sat, Jan 11, 2020 at 12:14 PM Paul King wrote: > > > Dear development community, > > I am happy to start the VOTE thread for a Groovy 2.4.18 bug fix release! > > This release includes 3 bug fixes/improvements as outlined in the changelog: > https://issues.apache.org/jira/secure/ReleaseNote.

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

+1 On Sun, Jan 12, 2020 at 9:12 AM Paul King wrote: > > > Dear development community, > > I am happy to start the VOTE thread for a Groovy 3.0.0-rc-3 release! > > This release includes 26 bug fixes/improvements as outlined in the changelog: > https://issues.apache.org/jira/secure/ReleaseNote.jspa

Re: jira changes

GitHub uses “help-wanted” which is a bit shorter and very clear. > On Jan 27, 2020, at 20:13, Paul King wrote: > >  > > * I created a 4.0.0-alpha-1 version number in Jira for changes fixed in master > * Nearly all of the 3.x roadmap issues have now been moved to 4.x (or > closed/adjusted i

Re: [VOTE] Release Apache Groovy 3.0.0

+1 On Fri, Feb 7, 2020 at 5:43 PM 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: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje

  1   2   >