I'm using TC 6.5.1 and struggling with the maven snapshot trigger. I spent pretty much time by investigating and testing with different tools (maven 2.2.1 and 3.0.3, nexus repository 1.9.2 and some older version) and found pretty easy scenario I would like to describe.
I have an artifact A snapshot and depending artifact B snapshot. I expect when I deploy the new snapshot version of A to repository, then B snapshot build is triggered. If I start TC server it actually happens, it computes the latest snapshot digest and builds the B as expected.
Unfortunately if I deploy new snapshot version of A to repository (TC is running) the B build is not triggered. I've checked the log and found out, that problem is, that
2011-07-28 10:05:05,251] DEBUG - .buildServer.maven.acd.Checker - Retrieved digest: 850a419a64caf0f3cbbdcf491baab4ebc85791fe SHA-1
returns the digest of not very latest version, even there is a newer snapshot version. If I checked the repository storage, I can see newer version(s).
To minimize the possibility of error in related tools (maven, nexus) I stop the TC and start again. Now I can see the different digest (which is actally correct and corresponds to the latest version)
[2011-07-28 10:16:21,745] DEBUG - .buildServer.maven.acd.Checker - Retrieved digest: 45adc19e3f2f1625653041ea2b9ba9835b42af92 SHA-1
TC is somehow able to get correct latest artifact (and its digest), but just after TC restart. Whatever change during TC run is not reflected.
Could you please advice me other steps/tests?