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 On 11 July 2014 14:04, Thomas Watson <[email protected]> wrote: > > > While investigating some changes to blueprint I noticed that the > blueprint-itests project pom refers to many old snapshot versions. Is this > normal? I would have expected it to refer to all the latest snapshot > versions that are in trunk for blueprint. As a result changes to add new > tests run against some old snapshot of the blueprint bundles. > > While trying to fix this to point to all the latest blueprint snapshots I > started to see test failures. This makes me question the stability of the > code in trunk since it seems we all are not really running the tests > against the latest blueprint bundles in trunk. > > Tom
