-
Notifications
You must be signed in to change notification settings - Fork 16
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
[JENKINS-73256] Migrate Jelly from EE 8 to EE 9 #114
Conversation
7574b7b
to
1f5f563
Compare
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.
Looks fine, security wise
SQL_MAXROWS_PARSE_ERROR=\ | ||
Error parsing 'javax.servlet.jsp.jstl.sql.maxRows' configuration setting: "{0}" | ||
Error parsing 'jakarta.servlet.jsp.jstl.sql.maxRows' configuration setting: "{0}" | ||
|
||
SQL_MAXROWS_INVALID=\ | ||
'javax.servlet.jsp.jstl.sql.maxRows' configuration setting neither an Integer nor a String | ||
'jakarta.servlet.jsp.jstl.sql.maxRows' configuration setting neither an Integer nor a String |
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.
We don't use jelly-sql
anywhere I think?
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.
Correct. This change is only for logical consistency with the jakarta.servlet.jsp.jstl-api
bump.
Context
Goes with three other pull requests:
Description
Replace dependencies with EE 9 versions in
pom.xml
and update all relevant imports.Testing done
Full PCT/ATH