Ish.  Because the ITs aren't 'submodules' they aren't going to automatically have the versions updated upon release, so we pass them in with variable substitution... which makes them not valid versions from eclipse/maven's perspective, un-modified by invoker.  It works nicely here because you really only have one, but for dagger, with a suite of these things, it's not a valid maven project. 

You need to be careful here, though, because if you don't do the passing in, you can have this test running against the wrong version once you release, so be sure to add the altering the version of this test's dependency on the processor artifact to the release process.  The release plugin by itself, I believe, does not update these.