>I made another commit so that .kt and .kts files are treated as text
Frankly speaking, we have * text=auto which means git would treat all
files as text if their first 8000 bytes does not have 00 byte.
In other words, kt files were already treated as text files.
>gradlew, sqlline, sqlsh
That
I didn't have core.eol in my git config; I was operating using the
default settings (for cygwin's git, anyway). I set 'core.eol=crlf' and
things improved.
I made another commit so that .kt and .kts files are treated as text
(therefore converted to Windows line endings on Windows), and shell
I had a similar problem. Try *removing core.eol *from your git config.
On Wed, Jan 29, 2020 at 10:03 AM Julian Hyde wrote:
> What is in the file is fine, and yet autostyle is complaining. So I
> think it is a bug in our autostyle setup.
>
> I can't figure out how to disable autostyle. I've
>yet autostyle is complaining
What is the exact error message?
>think it is a bug in our autostyle setup
The idea behind that is it should discover most settings from Git
configuration (e.g. git global config options), .gitattributes,
.editorconfig, and so on.
> I've tried things like "gradlew
What is in the file is fine, and yet autostyle is complaining. So I
think it is a bug in our autostyle setup.
I can't figure out how to disable autostyle. I've tried things like
"gradlew -PskipAutostyle".
Julian
On Tue, Jan 28, 2020 at 11:39 PM Vladimir Sitnikov
wrote:
>
> I guess it expects
I guess it expects EOL to match Git configuration.
>Autostyle seems to expect \n at the ends of lines and get \r\n, or vice
versa
I guess it should show what is in the file, and what it expects.
Vladimir
I'm running the build on Windows and getting autostyle failures. I'm
using cygwin but otherwise it is a standard build. What am I doing
wrong?
$ java -version
java version "13.0.2" 2020-01-14
$ git clone https://github.com/apache/calcite.git
$ cd calcite
$ ./gradlew build
Execution failed for
