Mailing-List: contact users-help@buildr.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@buildr.apache.org
Received-SPF: pass (nike.apache.org: domain of alex.boisvert@gmail.com
 designates 209.85.216.179 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=kAurKBF14TYv061F9Wu2xTb6LhIp22sSfT0iDYq+xHwjDdmhCi2Eu24C8lk2HK13SL
         3iNLbQXH66crgAD9Mvn+Ihw7EqjOrou/AlcfdKu9Zkm3eFdaRFuI2jN+y3Ooflkzc4po
         AltdlPwfE/+enf1rsssTR/RGZ49vFZk/UoMJg=
MIME-Version: 1.0
In-Reply-To: <C873796D.4329%andrew@monkeybroker.com>
References: <C873796D.4329%andrew@monkeybroker.com>
Date: Mon, 26 Jul 2010 17:12:09 -0700
Message-ID: <AANLkTim2HAurwinAwTJDG93ZSqFcE=F57vRcgveNTXzT@mail.gmail.com>
Subject: Re: Constant compiling
From: Alex Boisvert <alex.boisvert@gmail.com>
To: users@buildr.apache.org
Content-Type: multipart/alternative; boundary=00c09fa21c202a657e048c535aa6

--00c09fa21c202a657e048c535aa6
Content-Type: text/plain; charset=ISO-8859-1

On Mon, Jul 26, 2010 at 2:42 PM, Andrew Watkins <andrew@monkeybroker.com>wrote:

> Hello,
>
> I have a custom task I created that makes use of Java::Commands.java to run
> the program.  Unfortunately, every time the taks is called, it recompiles
> first.  This is because buildr is detecting a missing class file, which is
> due to a weird way in which one of the developers decided to write the class
> with traits, etc.  Is there a way to forcibly stop buildr from recompiling?
>  Like task :heartbeat, :compile => false do ... Or something?
>

You could fiddle with either:

   - the compile task's list of prerequisites (e.g.
compile.prerequisites.delete
   "foo")
   - your custom's tasks list of prerequisites
   - timestamps on the file system (or creating missing files)
   - ...

really depends on the specifics of your project.  A more tangible problem
description would help.

alex

--00c09fa21c202a657e048c535aa6--