Open daliboris opened 1 year ago
After some time of coding, the problem with the application generation error reappeared and changing EOL in the config.xqm
file didn't help.
Workaround of this problem was generating the TEI Lex-0 application using GitHub Actions and installing the application back on the eXist-db.
The comparison between local files and files in generated package was obvious: local files used CRLF line encoding, generated files LF.
Promissing and long-term solution: changing EOL in all module files + setting LF for the workspace in Visual Studion Code: "files.eol": "\n",
For changing all file on Windows machine I used solution described in StackOverflow:
Prerequsities:
EOL Conversion
modules
directory$path = Get-Location
# These files are not in the `modules` directory, just to be sure
$exclude_patterns = "^.*(\.git|\.idea|node_modules|\.next|\.(jpeg|jpg|png|gif|mp4|mkv|mp3|wav)$).*$"
# Find files to convert
$files = Get-ChildItem -Path $path -Recurse -Include *.* -File -Force | Where-Object {$_.FullName -notmatch $exclude_patterns}
Write-Host "Found $($files.Count) files"
$files | ForEach-Object { dos2unix $_.FullName }
All files have been converted and even synchronized with the eXist-db server.
The solution used by Luka (from Slack):
After replacing the whole modules
folder with the one on GitHub I can generate new applications, so that fixed it.
@line-o are you aware of this? Could this be fixed on roasters end? Should the bug move there?
When the
\templates\basic\modules\config.xqm
file is uploaded on the server with CRLF end of lines (on Windows) the TEI Publisher is unabled to generate an application.The generation ends with the following exception thrown in the Roaster.
If EOL is changed to LF, TEI Publisher can generate applications as usual.