Build fails on Windows if you cloned with autocrlf=input, eol=lf #10398
Labels
Comments
DamnClin
added
area: bug 🐛
|
|
Eulbobo
added a commit
to Eulbobo/jhipster-lite
that referenced
this issue
Jul 31, 2024
Changing end of file and properties String manipulation to use Properties class close jhipster#10398
Eulbobo
added a commit
to Eulbobo/jhipster-lite
that referenced
this issue
Jul 31, 2024
Changing end of file and properties String manipulation to use Properties class close jhipster#10398
Eulbobo
added a commit
to Eulbobo/jhipster-lite
that referenced
this issue
Jul 31, 2024
Changing end of file and properties String manipulation to use Properties class close jhipster#10398
I know your pain! It's good to have someone with this setup to ensure the project is working on it. I started using WSL on Windows to avoid Windows-only issues 😅, and to use the Bash scripts more easily on Linux. In my tests, WSL was faster. I talked about it here. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Some implementations relies on System.lineSeparator() to split configuration file lines
If you are running on Windows, your default lineSeparator is
\n\r, but, if you cloned the project with LF end of lines, the split can't be done anymore and build failsIssue #477 provided an improved way to deal with end of lines, so it may be the solution
Maybe I'm the only one using this setup, but I'll try and fix it anyway
The text was updated successfully, but these errors were encountered: