[jira] Commented: (MRELEASE-655) Maven Release Plugin Fails to perform the Release when using TFS scm

2011-08-12 Thread Dmitry Malenok (JIRA)

[ 
https://jira.codehaus.org/browse/MRELEASE-655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=275689#comment-275689
 ] 

Dmitry Malenok commented on MRELEASE-655:
-

Workaroud: use Cross-platform command-line client for Team Foundation Server 
(from Microsoft Visual Studio Team Explorer Everywhere 2010) instead of native 
TFS command line utilites.
Details: 
http://social.msdn.microsoft.com/Forums/en-AU/tee/thread/8ea3796d-acdd-4ec8-9c44-d9599512b0bb

 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




[jira] Commented: (MRELEASE-552) Add useEditMode option to release:update-versions

2011-08-12 Thread Dmitry Malenok (JIRA)

[ 
https://jira.codehaus.org/browse/MRELEASE-552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=275697#comment-275697
 ] 

Dmitry Malenok commented on MRELEASE-552:
-

This issue is a bug, but not an improvement. It is near to impossible to reset 
the readonly flag manually for the huge multi-modules project :(

 Add useEditMode option to release:update-versions
 -

 Key: MRELEASE-552
 URL: https://jira.codehaus.org/browse/MRELEASE-552
 Project: Maven 2.x Release Plugin
  Issue Type: Improvement
Affects Versions: 2.0
Reporter: Russ Kociuba
Priority: Minor
 Attachments: MRELEASE-552.patch


 My SCM (TFS) needs to checkout files in order to be able to edit them.  Thus 
 the current version of the
 update-versions goal fails because the files are read-only.  The ability to 
 set the useEditMode option to true would fix this.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] Created: (SUREFIRE-740) Fractional part of method execution time is truncated for non English locale

2011-05-18 Thread Dmitry Malenok (JIRA)
Fractional part of method execution time is truncated for non English locale


 Key: SUREFIRE-740
 URL: http://jira.codehaus.org/browse/SUREFIRE-740
 Project: Maven Surefire
  Issue Type: Bug
  Components: Maven Surefire Report Plugin
Affects Versions: 2.8.1
 Environment: Windows 7 Pro x64 with Russian locale/JDK 1.6.0_21/Apache 
Maven 3.0.3 (r1075438; 2011-02-28 20:31:09+0300)
Reporter: Dmitry Malenok


The problem is that Maven Surefire Plugin and Maven Surefire Report Plugin use 
different locales for writing and reading TEST-* file if the default locale is 
not set to English locale.The first one always uses Locale.ENGLISH 
(org.apache.maven.surefire.report.AbstractReporter, line 43), but the second 
one uses the default locale 
(org.apache.maven.plugins.surefire.report.TestSuiteXmlParser, line 50). Russian 
and English locale use different decimal symbol (, - Russian locale, '.' - 
English locale) that causes the described problem.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira