I'm trying to do a Remote Run on a Maven configuration on TC 5.1.
The pom.xml is part of the changes to commit and contains an upgrade from Spring lib from 2.5.6 to 3.0.2.
The build fails because of some library conflicts, I've check the clean file option on a check out on Agent config, added the maven goal clear, but all to no avail.
When I verify the check out directory, look at the pom, it's not the one I want to commit, it's the previous version.
During a Remote Run, I assume the files are freshly checked out from VCS then the modified files are added on top, so that an Agent can run a Maven build in a directory that would mirror what's on the working copy.
Is there something I am missing here? I though the agent check out directory would be exactly my working copy that I'm trying to commit.
The build runs fine on the working copy, only the remote run fails.
Thanks for helping