-
Notifications
You must be signed in to change notification settings - Fork 60
Normalization: Ensure end of file markers per git standards and tabs as spaces #361
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
base: master
Are you sure you want to change the base?
Conversation
@hazendaz please look at build result |
Test failures look related:
|
w
when shell parses the here-doc |
so we need to use a tab character with |
I believe its fixed now, I removed the leading space from END. |
@@ -202,19 +202,19 @@ elif set_java_home; then | |||
javaSource="$TMP_DOWNLOAD_DIR/Downloader.java" | |||
targetZip="$TMP_DOWNLOAD_DIR/$distributionUrlName" | |||
cat >"$javaSource" <<-END |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we use <<END
as we don't have a tabs now?
While reviewing repo, detected 2 files with tab characters instead of spaces and 20 other files that did not adhere to git expectations of empty line at end of file. This is a no-opt change that ensures the entire repo follows same standard as all other files complied.