On Sat, Jan 03, 2015 at 08:49PM, Roman Shaposhnik wrote: > Hi! > > there was a thread recently that suggested Graddle > as a great place for all the snippets of code we need > for the common tasks around Bigtop (test execution, > puppet, etc.). I've started to play with the idea for > my build stuff and ran into a slight issue. > > I can't quite figure out what's the best way to pass > arguments to the scripts that I'm now turning into > gradle tasks. > > I guess I can do this: > $ gradle puppet-deploy -Dfoo=bar ... > but it feels awkward (most because there's > not even a chance for any kind of help being > printed out on task usage).
Are you referring to a task usage info? Do you think adding some info into a task description will be sufficient? If not, I'd consider adding a new task that will be printing out tasks usage? The usage info could be stored in a separate file perhaps? Or am I barking on a wrong tree? Cos
signature.asc
Description: Digital signature
