-
Notifications
You must be signed in to change notification settings - Fork 110
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
Fix el issue 194 #1159
Fix el issue 194 #1159
Conversation
The third (elp2) and fourth (elp3) tests weren't testing what was intended.
The result from this test may be unexpected. See the note in the block comment just above the test.
I tried testing this in local by copying the changes in this PR manually over #1164. I was getting below when run with glassfish 7.
Not sure if I did anything wrong. Can you help confirm if this change works for other implementations or need any other change to pass (or applicable only for EL 6.0?) |
This change is intended for EL 6.0 / Jakarta 11 onwards since it changes what is being tested. Compatible Jakarta EE 10 implementations should pass the updated tests but it is possible that they do not. |
To update this, I am running the EL tests from the refactored branch against Tomcat and I am seeing test failures. I'm not sure what the root cause is yet. |
Based on my run with Glassfish8 (jakarta.el-api.version 6.0.0-M1) ELClientIT.elCoerceLambdaExpressionToFunctionalInterfaceTest is the only failure with below exception. Do you see any other failures ?
|
Yes, that is the failure. Assuming that a further PR is going to be required, do you want it against master or tckrefactor? |
And on the subject of tckrefactor, are there any plans to move the EL TCK to the EL project? |
New PR against tckrefactor will be convenient. The current plan is to stage a new refactored EL TCK from tckrefactor branch for EE11. |
ACK. Expect some new PRs shortly. I think this one can be closed unless you need to keep it open for any reason. |
There are no plans as of now, but after the refactoring it should be easier to move the standalone EL sources to a different repository. The same EL tests are also run as part of platform TCK in servlet & JSP containers , we have not found the right approach to refactor such runs yet. Until that IMHO it would be apt to keep these tests in this repository.
Thanks! Yes, this PR can be closed. |
Remaining work completed via #1215 |
Fixes Issue
jakartaee/expression-language#194
Related Issue(s)
None
Describe the change
There are two parts to this PR
Additional context
None
CC @alwin-joseph @anajosep @arjantijms @cesarhernandezgt @dblevins @m0mus @edbratt @gurunrao @jansupol @jgallimore @kazumura @kwsutter @LanceAndersen @bhatpmk @RohitKumarJain @shighbar @gthoman @brideck @OndroMih @dmatej
@starksm64 @scottmarlow