Hi Thomas,
It was like this before the latest changes. AFAIU, the purpose is to
test the target artifacts, so I would agree to update the itests with
the latest SNAPSHOTs (at least for the current module) to test the codebase.
If the team is OK with that, I will do the changes (after the current
releases votes).
Regards
JB
On 07/11/2014 03:04 PM, Thomas Watson 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
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
