Comments for The Kaptain on ... stuff

Comment on Five Cool Things You Can Do With Groovy Scripts by » Blog Archive

» Blog Archive — Tue, 13 Dec 2011 22:50:41 +0000

[...] Five Cool Things You Can Do With Groovy Scripts [...]

Comment on Groovy CliBuilder with multiple arguments by Starr

Starr — Fri, 25 Nov 2011 04:30:18 +0000

I would really like to thank you such a lot of for your job you have made in writing this blog post. I am hoping the same top work from you later on also.

Comment on Groovy CliBuilder with multiple arguments by TheKaptain

TheKaptain — Sun, 06 Nov 2011 20:09:23 +0000

There’s actually an example of using the commons-cli directly(without CliBuilder) in the Groovy source code that might help you as well:
https://github.com/groovy/groovy-core/blob/master/src/main/org/codehaus/groovy/tools/GrapeMain.groovy

Comment on Groovy CliBuilder with multiple arguments by TheKaptain

TheKaptain — Sun, 06 Nov 2011 19:54:35 +0000

It should be, although I can’t find a convenient example. Under the hood you’re using the common-cli-1.2 jar, so you should be able to do everything it supports, although the syntax might not work directly on the builder.

Comment on Groovy CliBuilder with multiple arguments by Pavel

Pavel — Sun, 06 Nov 2011 16:25:01 +0000

Hi! Is there a way to create mutually exclusive options using CliBuilder (like using OptionGroup in apache cli) ?

Thank you!

Comment on Groovy inspect()/Eval for Externalizing Data by Hassan Jawad

Hassan Jawad — Sun, 16 Oct 2011 23:19:43 +0000

Thanks awesome information love this post

Comment on A Groovy/Gradle JSLint Plugin by GroovyMag - the magazine for Groovy and Grails developers about Groovy programming and Grails development

Tue, 05 Apr 2011 19:31:21 +0000

[...] Kelly Robinson shows how to create a plugin for Gradle.

Comment on Bamboo, Grails and Git for Continuous Integration by Benny's Blog

Benny's Blog — Fri, 01 Apr 2011 20:06:53 +0000

Atlassian Bamboo, multiple projects, one repository and shared libraries…

Having several projects in Bamboo that share a repository, build script and libraries, it can be tricky to configure Bamboo build plans correctly; but it isn’t hard at all. Here’s a quick walkthrough…….

Comment on Hooking into the Jenkins(Hudson) API by Blog bookmarks 03/29/2011 « My Diigo bookmarks

Blog bookmarks 03/29/2011 « My Diigo bookmarks — Tue, 29 Mar 2011 04:35:02 +0000

[...] Hooking into the Jenkins(Hudson) API | The Kaptain on … stuff [...]

Comment on Hooking into the Jenkins(Hudson) API by Ray

Ray — Mon, 28 Mar 2011 20:47:58 +0000

Thanks for this! Looks to be very easy to use API.

Comment on Groovy CliBuilder with multiple arguments by TheKaptain

TheKaptain — Fri, 04 Feb 2011 03:08:58 +0000

Hmmm, not sure what’s happening there. Using Groovy 1.7.6 with exactly this code I get the following(expected) output.

groovy test.groovy -o out -i f1 f2 f3
[f1, f2, f3]

Comment on Groovy CliBuilder with multiple arguments by jianping

jianping — Thu, 03 Feb 2011 20:44:22 +0000

use unlimited option with default valueSeparator space seems to have some problem: I got extra ‘–’ between the first and second parameters:

-o out -i f1 f2 f3

{code}

def cli = new CliBuilder(usage: “help”)
cli.o(argName:’outputFile’, longOpt:’output’, required:true, args:1, ‘Output File’)
cli.i(argName:’inputFiles’, longOpt:’inputs’, required:true, args: Option.UNLIMITED_VALUES, ‘Input Files’)

// process the args from the second element, leaving the name of the command out.
def options = cli.parse(args)

if (!options)
{
return
}

println (options.is)

{code}

Comment on Groovy CliBuilder with multiple arguments by TheKaptain

TheKaptain — Thu, 03 Feb 2011 18:41:51 +0000

The Apache cli library is actually fairly well documented, including the Options JP, but as I recall I did have to look around the inet awhile to find good examples:
http://commons.apache.org/cli/introduction.html

Comment on Groovy CliBuilder with multiple arguments by jianping

jianping — Thu, 03 Feb 2011 18:35:33 +0000

Good post, Kelly. Why is Option.UNLIMITED_VALUES not documented anywhere?

Comment on Groovy inspect()/Eval for Externalizing Data by TheKaptain

TheKaptain — Mon, 17 Jan 2011 17:26:49 +0000

Thanks Hans, and that’s exactly the way I’ve gone since writing this. Here’s the Closure that I’m using as part of a regular developer build:
def tolerance = 2000 final Closure testLogger = { descr, result -> def time = result.endTime - result.startTime if (time > tolerance) { logger.warn("Test: ${descr.className}.${descr.name} is long running: ${time / 1000} s") } }