Comments on: Build Refactoring: Extract Target

By: Build Refactoring

Build Refactoring — Sun, 17 Jan 2010 13:02:11 +0000

[...] write about it here and here and [...]

By: Build Refactoring: Delete Boolean Property — The Build Doctor

Build Refactoring: Delete Boolean Property — The Build Doctor — Fri, 19 Dec 2008 16:07:19 +0000

[...] time, you read about the extract target refactoring. Today, I’m going to show you one that I love to perform: delete boolean [...]

By: simpsonjulian

simpsonjulian — Fri, 19 Dec 2008 12:11:08 +0000

I prefer Julian’s approach, obviously Agree with Andy that one target should do one thing. The argument about placing dependencies in targets or in a target that does flow control will run and run. I can’t help feeling that we need better editors for all this. The Eclipse Ant editor is the most helpful (I use it for NAnt as well) – it allows you to complete on target and property names. Still nothing actually shows you the dependency graph as you edit. That would be sweet.

By: Mike Williams

Mike Williams — Wed, 10 Dec 2008 12:30:12 +0000

@Andy: I think the pattern you’re describing actually does more harm than good, because it removes the dependency information from where it belongs (on each target) and treats Ant more like a procedural scripting language. I prefer Julian’s approach.

By: Andy Palmer

Andy Palmer — Wed, 10 Dec 2008 00:24:29 +0000

Dan North showed me a nice pattern where each of the build targets does one thing, and the rule target (default in this case) is responsible for determining the order.
That way, you can see the order of targets at a glance, without having to follow each build target through it’s dependencies