On 26/06/2012, at 10:34 AM, Luke Daley wrote: > > > > > On 25/06/2012, at 12:59 PM, Adam Murdoch <[email protected]> wrote: > >> >> On 26/06/2012, at 12:38 AM, Luke Daley wrote: >> >>> I'm seeing more and more that people are manually executing tasks, for >>> usually understandable reasons and we talked about this earlier. >> >> This person should be using dependsOn for the problem below. It's a >> straight-ahead dependency, in particular given that they want to make the >> result of the filtering available to other tasks. > > Yeah, which makes it worse as this person has no indication that they should > do this.
Do you mean no indication at runtime? There are, of course, a bunch of tutorials and samples and other docs that show you how to chop up your logic into tasks and wire them together. But that doesn't seem to have helped in this case. > >> >> >>> >>> I think we should spit a warning in this case that this is not a good thing >>> to do. >> >> Probably. I've been waiting until we have some kind of replacement before >> doing that. > > Waiting for a replacement sounds right, as long as that doesn't mean waiting > too long :) > >> >> >>> I anticipate that this will have as much or more pushback than the >>> introduction of extra properties. >>> >>> Begin forwarded message: >>> >>>> From: Gradle <[email protected]> >>>> Date: 25 June 2012 3:10:10 AM PDT >>>> To: [email protected] >>>> Subject: New problem: Resources filtering in jettyRun task >>>> >>>> Opal just reported this problem in Gradle: >>>> >>>> Resources filtering in jettyRun task >>>> >>>> Hi, >>>> In my project I've a dedicated task to compile coffee script code, run >>>> jetty and test site in browser. Here it is: >>>> >>>> task testClient { >>>> copyJs.execute() >>>> jettyRun.daemon = true >>>> jettyRun.execute() >>>> def proc = 'coffee -o src/main/webapp/js -cw src/main/coffee'.execute() >>>> handle_proc(proc) >>>> } >>>> >>>> In the mentioned task is use mocks (written in javascript) in index.html >>>> and this is the only task I want these lines: >>>> >>>> to be present in index.html. >>>> >>>> First question is how to filter index.html in the mentioned task to make >>>> these lines present (no filter function in jettRun) ? >>>> Second question is how to organize this filtering to be accessible form >>>> other tasks? As I said before, I want to include these lines in testClient >>>> as well as exclude them from any other task (such as war for instance). >>>> Reply | Notify me when people reply >>>> >>>> This message sent from the Gradle community on Get Satisfaction. >>>> To unsubscribe or change your email settings, click here. >>>> >>>> >>>> ---------------- >>>> Create a customer community for your company at GetSatisfaction.com. >>>> >> >> >> -- >> Adam Murdoch >> Gradle Co-founder >> http://www.gradle.org >> VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting >> http://www.gradleware.com >> -- Adam Murdoch Gradle Co-founder http://www.gradle.org VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting http://www.gradleware.com
