You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After nacos is packaged, the /bin/sh^M problem will appear when executing the shell script on Linux. This is caused by script line breaks instead of LF. I checked the script in the source code and found that startup.sh and shutdown.sh are CRLF formatted line breaks
ERROR OS=Windows and the assembly descriptor contains a *nix-specific root-relative-reference. This error occurs during binary packaging in Maven, but it will not affect the packaging. I queried the documentation and found that the reason is: because the assembly task is executed on Windows, but it contains a path relative to Linux.
Describe what you expected to happen
I submitted a PR and revised the above two questions
Format startup.sh and shutdown.sh. Use Unix/Linux standard line break LF to avoid converting line breaks during execution, and tested on Linux and Unix.
Solve the OS=Windows error when packaging Maven. Successfully packaged on Linux and Windows
Tell us your environment
JDK 1.8
CentOS 6.9
The text was updated successfully, but these errors were encountered:
…ux (#3371)
* Replace RuntimeException caused by HealthCheckerFactory with Nacos serialization exception
* 1. Format startup.sh and shutdown.sh. Use Unix/Linux standard newline LF
2. Solve the OS = Windows error when packaging Maven (does not affect packaging)
Issue Description
Type: Bug Report
Describe what happened (or what feature you want)
ERROR OS=Windows and the assembly descriptor contains a *nix-specific root-relative-reference
. This error occurs during binary packaging in Maven, but it will not affect the packaging. I queried the documentation and found that the reason is: because the assembly task is executed on Windows, but it contains a path relative to Linux.Describe what you expected to happen
I submitted a PR and revised the above two questions
Tell us your environment
The text was updated successfully, but these errors were encountered: