You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@jackrabbit.apache.org by re...@apache.org on 2021/11/16 14:42:17 UTC

svn commit: r1895086 - /jackrabbit/site/trunk/src/site/markdown/creating-releases.md

Author: reschke
Date: Tue Nov 16 14:42:17 2021
New Revision: 1895086

URL: http://svn.apache.org/viewvc?rev=1895086&view=rev
Log:
note that the Cygwin workaround for SVN works for Git as well

Modified:
    jackrabbit/site/trunk/src/site/markdown/creating-releases.md

Modified: jackrabbit/site/trunk/src/site/markdown/creating-releases.md
URL: http://svn.apache.org/viewvc/jackrabbit/site/trunk/src/site/markdown/creating-releases.md?rev=1895086&r1=1895085&r2=1895086&view=diff
==============================================================================
--- jackrabbit/site/trunk/src/site/markdown/creating-releases.md (original)
+++ jackrabbit/site/trunk/src/site/markdown/creating-releases.md Tue Nov 16 14:42:17 2021
@@ -263,7 +263,7 @@ You need to change the `~/.m2/settings.x
 Appendix C: Cygwin
 ------------------
 
-The Subversion support in the release plugin assumes platform-specific path delimiters, and thus does not work properly if the "svn" executable is the Cygwin version. The easiest workaround for this problem is to install a Windows-native SVN version as well, and to modify the PATH variable for the mvn invocation so that it's found instead of the Cygwin variant.
+The Subversion and Git support in the release plugin assumes platform-specific path delimiters, and thus does not work properly if the "git" or "svn" executable is the Cygwin version. The easiest workaround for this problem is to install a Windows-native GIT or SVN version as well, and to modify the PATH variable for the git/mvn invocation so that it's found instead of the Cygwin variant.
 
 Appendix D: Branching
 ---------------------