New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cygwin classpath problem #735
Labels
Milestone
Comments
Thanks for the report. Could you try to isolate the exact problem? |
lrozek
added a commit
to lrozek/flyway
that referenced
this issue
Apr 24, 2014
Hi Alex, the problem was that when it was run under cygwin, you still should use windows classpath separator instead of linux one. |
axelfontaine
pushed a commit
that referenced
this issue
Apr 25, 2014
#735 fixing issue with classpath separator
Thanks for the fix! Merged. |
sguillope
added a commit
to sguillope/flyway
that referenced
this issue
Nov 6, 2015
New Git Bash for Windows (https://git-for-windows.github.io/) is recognized as "MINGW..." system. For example on my test machine `uname` returns the following: $ uname MINGW64_NT-6.1 This patch expands on the fix done in flyway#735 to use Windows classpath separator when running in Git Bash for Windows.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In a cygwin shell under Windows Server 2008 R2 Standart try to run following: "./flyway" without quotes.
$ ./flyway
Error: Could not find or load main class org.flywaydb.commandline.Main
Related reference:
http://stackoverflow.com/questions/17433449/flyway-error-on-cygwin
#562
#603
The text was updated successfully, but these errors were encountered: