On Wed, Aug 25, 2010 at 10:40 PM, Adam Murdoch <[email protected]> wrote:
> Looking at your source, your task doesn't actually do anything. So, the > first time you run it, Gradle remembers the input files and notes the fact > that the task didn't produce any output files. Next time you run it with the > same inputs, Gradle will skip the task because it knows the task does not do > anything with those particular inputs - regardless of whether the build dir > exists or not. > > You might change the task to create a dummy file in the destination > directory if you want it to be re-executed after a clean. > > One thing that Gradle doesn't do, which it should, is to re-execute the > task if it's implementation class has changed. So, after you make the change > above, you should run gradle -C rebuild clean to clear up the state that > Gradle has cached. You only need to do this once. > Hooray! That did it! Thank you so much. Small fyi, I also needed to create a test javascript file in src/main/javascript otherwise it doesn't execute the compile task. Note that it doesn't complain about that at all unless I use the -d option. Perhaps what ever is using/evaluating the @SkipWhenEmpty annotation should warn/print when empty? Thanks again for the help. I should be able to move forward with the plugin now. Cheers, Eric -- Learn from the past. Live in the present. Plan for the future. Blog: http://www.townsfolkdesigns.com/blogs/elberry jEdit <http://www.jedit.org> - Programmer's Text Editor Bazaar <http://bazaar.canonical.com> - Version Control for Humans
