Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Incomplete
-
1.8
-
None
-
None
-
Patch
Description
I have a case where I have a build agreggator that's not a hierarchical parent for the modules.
I mean, I have $project/build-agg, $project/module-1, $project/module-2 and etc.
When I release just one module it tries to tag $project/module and it works fine.
However, when I try to release the whole project and tag $project, I run the release goal from $project/build-agg and it gets lost in tag phase when looking for the $project url at the given workspace.
"A client error occurred: The Team Foundation Server project collection URL to use could not be determined the options or argument paths provided. Specify a login profile or workspace, or use the 'collection' option."
I added the following code at line 87 of the TfsTagCommand.java file to solve my problem:
command.addArgument("-server:" + tfsRepo.getTfsUrl());
with that argument the "tf label" command worked.