On Thu, Feb 19, 2009 at 12:06 AM, Ryan D.
test.libs << ‘ext’
task :test => :clean DOES work, just before the fact, not after.
to do after you attach another task to the same name:
task :test do
The after here is a placeholder for code, right? It can’t be a task name
since a task does not define a method which can be invoked like that, at
least not with the Rake I’ve got installed on my maching.
Unless I’m missing something this is effectively the same thing as one
task with the code from both inside the block.
It works but…
that said… why are you cleaning afterwards? I can imagine a number of
situations where that will screw you up. You probably DO want to put :clean
(pre) dependencies on a number of your tasks like packaging and stuff, but
having it after your test could introduce some hiccups.
The way I’d approach this would be to have tasks for whatever sequences
subtasks make sense, so something like:
desc “clean up”
task :clean do |t|
puts “cleaning up”
task :test do |t|
desc “test and clean up”
task :test_and_cleanup => [:test, :clean]
desc “clean up then test”
task :cleanup_and_test => [:clean, :test]
Task names could be adjusted, so if you wanted to normally clean up and
test, or test and then clean up you could rename
the ‘normal’ task, .e.g :test becomes something like :test_only and
:cleanup_and_test becomes :test