Closed mbrandl87 closed 1 year ago
From cmd or Powershell it doesn't work at all at the moment, I'm getting hit by #22979
This bug is supposed to be fixed. You should open a new issue with a reproduction.
Autocrlf now uses relative path. This issue is probably fixed.
Overview of the issue
When I try to generate a new Entity or regenerate an existing one, in conjunction with the --auto-crlf option, the generator bails out with $somefile is outside of repository. If I omit the option it works, regenerating to much because of the CRLFs.
Motivation for or Use Case
Due to Eclipse constantly changing LF to CRLF although told to use LF, we need the possibility to let JHipster use CRLF in our windows workspaces.
Reproduce the error
In Cygwin run jhipster entity Bla --auto-crlf Answer yes to regenerate, or just at any field so it has something to generate here :)
From cmd or Powershell it doesn't work at all at the moment, I'm getting hit by #22979
Suggest a Fix
JHipster Version(s)
8.0-beta.3
**JH├─┬ generator-jhipster-entity-audit@5.0.0-beta.1 extraneous
│ └── generator-jhipster@8.0.0-beta.3 deduped └── generator-jhipster@8.0.0-beta.3