Mailing-List: contact users-help@buildr.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@buildr.apache.org
Received-SPF: pass (athena.apache.org: domain of gcptbu-users@m.gmane.org
 designates 80.91.229.3 as permitted sender)
To: users@buildr.apache.org
From: Adam George <atg103@googlemail.com>
Subject: Re: Correct Use of the 'tap' Method
Date: Thu, 23 May 2013 16:10:00 +0000 (UTC)
Lines: 31
Message-ID: <loom.20130523T175603-978@post.gmane.org>
References: <loom.20130523T150915-930@post.gmane.org>
 <CAKz=cCagt3hChW82QBO9SxNxmY2Jy9xV_nToRN_PyiPs62Y1Vg@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
User-Agent: Loom/3.14 (http://gmane.org/)

Antoine Toulme <antoine@...> writes:

> 
> This is more of a Rake question actually. Rake provides ways for you to
> define tasks.
> So when you type task(:compile) do |task| ... you are actually redefining
> the compile task. That's why it's doing nothing.
> 
> Rake provides a way to define task dependencies as tasks. Buildr builds on
> this by adding the tap method which lets you add a dependent task directly
> on the compile task. tap inserts the dependency as the first item in the
> list, so if you tap twice, the second time will execute before the first
> time.
> 
> I hope this helps.
> 

Hi Antoine,

Thanks, that does make some sense, and it's useful to know about the
double-tapping!  However, I am now confused about how the compile task
worked at all if I was redefining it.

In example 1 (without .tap) the compilation was still working with the
default behaviour (compiling from src/main/java).  How is this possible if
the task has been redefined to be something else by my code?

Thanks,

Adam