On Mon, Jul 26, 2010 at 2:42 PM, Andrew Watkins <[email protected]>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
