[
https://issues.apache.org/jira/browse/SCM-699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated SCM-699:
-------------------------------
Fix Version/s: waiting-for-feedback
> Case corner when tagging a release with build-agreggator that's not
> hierchical parent to modules.
> -------------------------------------------------------------------------------------------------
>
> Key: SCM-699
> URL: https://issues.apache.org/jira/browse/SCM-699
> Project: Maven SCM
> Issue Type: Improvement
> Components: maven-scm-provider-tfs
> Affects Versions: 1.8
> Reporter: Jose Rodolfo Freitas
> Priority: Major
> Fix For: waiting-for-feedback
>
> Attachments: TfsTagCommand.java
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
