Details
-
Improvement
-
Status: Closed
-
Minor
-
Resolution: Won't Fix
-
None
-
None
-
None
Description
As mentioned in SCM-213, the Maven release plugin breaks when using Cygwin's svn. There is a workaround to use a Windows Subversion client instead. Since the documentation lists useCygwinPath as an option it would be good if it worked everywhere. I checked the source and useCygwinPath only appears to be used in the Update command. Either the docs should clarify where it can be used or (ideally) it could be used for Commit and Checkout too.
Attachments
Issue Links
- relates to
-
MRELEASE-146 Release tag with SVN under Cygwin fails when sending the svn command a bad absolute path
- Closed
-
SCM-213 Broken with Cygwin
- Closed