You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Stephen Connolly (JIRA)" <ji...@codehaus.org> on 2011/07/01 11:03:42 UTC
[jira] Updated: (MRELEASE-655) Maven Release Plugin Fails to
perform the Release when using TFS scm
[ https://jira.codehaus.org/browse/MRELEASE-655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stephen Connolly updated MRELEASE-655:
--------------------------------------
Labels: scrub-review-started (was: )
I cannot make sense of what the issue is...
It would help if you gave the command sequence that is being used and the command sequence which should be used, and not as an attachment but as a simple numbered list in a comment.
Better still would be a test case, but as most of us don't have TFS, it will really take somebody who has TFS to create a patch... also I suspect this is an issue with maven-scm not the release plugin.
> Maven Release Plugin Fails to perform the Release when using TFS scm
> --------------------------------------------------------------------
>
> Key: MRELEASE-655
> URL: https://jira.codehaus.org/browse/MRELEASE-655
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: perform
> Affects Versions: 2.1
> Environment: Windows 7 64 bit, Maven 3.0.1, Java 1.6_23, TFS 2010
> Reporter: Nikhil Jain
> Priority: Blocker
> Labels: scrub-review-started
> Attachments: keymanager-release.log, Release_Command.txt
>
>
> We are able to prepare a build successfully using Prepare release but while performing release the release plugin is not able to perform release using TFS 2010. It errors due to incorrect sequence of SCM commands for TFS. The output of perform release is attached.
> For performing release we are issuing a command while specifies to use edit mode, Provides anew TFS workspace to map and a working directory to checkout code to perform a release.
> We are using the release plugin with TFS as suggested on Teamprise site http://kb.teamprise.com/article/view/95
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira