-
Notifications
You must be signed in to change notification settings - Fork 5
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
Forward JAR options without changing order to classpath #990
Labels
refactoring
Code improvement without behavior change
Comments
tomuben
changed the title
Support escape sequence for ending white spaces in JAR option
Forward JAR options as is to classpath
Oct 23, 2024
tomuben
changed the title
Forward JAR options as is to classpath
Forward JAR options without changing order to classpath
Oct 23, 2024
tomuben
added a commit
to exasol/script-languages
that referenced
this issue
Oct 24, 2024
tomuben
added a commit
to exasol/script-languages
that referenced
this issue
Oct 25, 2024
related to exasol/script-languages-release#990 --------- Co-authored-by: Torsten Kilias <tkilias@users.noreply.github.com>
tomuben
added a commit
to exasol/script-languages
that referenced
this issue
Oct 29, 2024
tomuben
added a commit
that referenced
this issue
Oct 29, 2024
10 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Background
The
%jar
option for Java UDF references external JAR files, see https://docs.exasol.com/db/latest/database_concepts/udf_scripts/adding_new_packages_script_languages.htm#AddingJavafilesjartoaJavaUDFFile paths under Linux support white spaces. However, we don't want to break compatiblity with the old parser syntax which always trimmed the JAR file path.
Also, the current implementation collects the JAR options in a
std::set
, in order to avoid duplicates. However, the classpath entries are then in an alphabetical order. The user looses control about the order of the classpath entries.Acceptance Criteria
The text was updated successfully, but these errors were encountered: