Hi Alex,
On Nov 18, 2009, at 11:16 AM, Alex Boisvert wrote:
On Wed, Nov 18, 2009 at 9:08 AM, Alex Boisvert <[email protected]
>wrote:
On Wed, Nov 18, 2009 at 9:02 AM, Greg Lucas <[email protected]>
wrote:
I'm running buildr 1.3.5 (on jruby) and trying to tests a specific
project. I can specify a pattern (package or class) and things
work fine.
I was thinking I could also run all tests for a single project
using e.g.
$buildr myproject:test
or just
$cd myproject
$buildr test
but either way it runs all the tests for all the upstream
dependencies as
well. Is that expected?
Only if the upstream dependencies have changed.
If they haven't, then there either an issue with the build/
buildfile itself
or a bug in Buildr. Details would help narrow it down.
Would people be interested in an option to test only the specified
test
targets?
e.g. buildr test=:only project:foo:test
Not sure about the syntax yet but that's the idea.
There was some previous discussion about this: http://markmail.org/search/#query
:%20Suppressing%20retesting%20when%20the%20buildfile%20changes+page:1+mid:yazlwofpeshafjme+state:results
I'm in favor of it.
Rhett
