Tom
Jeremy Hughes <[email protected]> wrote on 07/11/2014 08:58:14 AM:
> Generally speaking, module dependencies on other Aries modules should
> be at the minimum required level for them to function correctly. Then
> using the -Pdev profile should bring those dependency versions up to
> the latest snapshot levels.
>
> blueprint-itests should be the same - when you run the tests with the
> default profile you're testing blueprint at the level that make all
> the tests work. This could include snapshots but not old snapshots of
> modules that have been released.
>
> Cheers,
> Jeremy
>
For compiling purposes I understand. But for itests I don't understand why
we would not want the tests to always run directly against what is built
from trunk. Otherwise how can we ensure we catch new bugs introduced in
trunk?
Tom