-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Upgrade to Spotless 2.0 #404
Comments
Just FYI, Spotless 2.0 is now available. I think right now you've got something like this: spotless {
...
lineEndings 'UNIX'
} You shouldn't need to specify lineEndings any longer - it will automatically use the same line endings policy as git. |
Hi @nedtwigg, Thanks for the heads up and congratulations on releasing Spotless 2.0! I just tried it locally, and it works fine. As for removing the explicit Can you please confirm the above assumption? Cheers, Sam |
in progress |
Due to the recent upgrade to Spotless 2.0, it should (theoretically) no longer be necessary to provide explicit `lineEndings` configuration. Issue: #404
The latest build on Windows just passed.... with the Spotless https://ci.appveyor.com/project/marcphilipp/junit5/build/101 So, maybe we can just assume it's working properly, ... but a confirmation would still be nice. 😉 |
You do have a .gitattributes file: https://github.com/junit-team/junit5/blob/master/.gitattributes, added in dc5e875 and so everything is working properly. If you didn't have a .gitattributes file, then git would check them out as Before spotless 2.0, it was really important to synchronize git and spotless on the line ending. Now they're always synchronized unless you go out of your way to manually specify a line ending to spotless. |
@nedtwigg, well... you're totally correct! I must be getting senile, since I'm the one who created that Thanks for reminding me, Sam |
Status Quo
Spotless 2.0 should fix issues regarding EOL characters on Windows (see diffplug/spotless#23).
Related Issues
Deliverables
The text was updated successfully, but these errors were encountered: