-
Notifications
You must be signed in to change notification settings - Fork 70
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
Feature/myfaces 4466: Merge Pull request into main (RC5 Target) - Faces.js new scripts! #514
Conversation
…ES-4456 # Conflicts: # api/src/main/javascript/META-INF/resources/myfaces/_impl/xhrCore/_AjaxUtils.js
* MYFACES-4468: Implement f:selectItemGroup * Create test for f:selectItemGroup * Resolve TCK signature failures (Remove Added Fields)
…ing import ranges in manifest
nonce handling in the new tests
integrated dom query sources, another fix for the nonce handling
updating from the github upstream project. Fix for an eval regression introduced by our nonce fixes (only the new codebase is affected) integratioin test 5, double eval failed because of it
updating to the latest mona-dish (no fixes but just to be in sync)
# Conflicts: # api/src/main/javascript/META-INF/resources/myfaces/_impl/_util/_Dom.js # api/src/main/javascript/META-INF/resources/myfaces/_impl/core/_EvalHandlers.js # api/src/main/javascript/META-INF/resources/myfaces/_impl/core/_Runtime.js
merging t-andraschkos changes with mine on the TCK 790... All TCKs pass as good as on the master now! Also mergin in the latest fixes for bugs reported by Tobago in the JS codebase
merging t-andraschkos changes with mine on the TCK 790... All TCKs pass as good as on the master now! Also mergin in the latest fixes for bugs reported by Tobago in the JS codebase
# Conflicts: # api/src/main/javascript/META-INF/resources/myfaces/_impl/xhrCore/_AjaxUtils.js # impl/src/main/java/org/apache/myfaces/component/validate/ValidateWholeBeanComponent.java
Update to the latest cleaned up codebase XhrFormData noa finally in a state I can live with all tests pass TCK as well!
fixing a test
For the sake of documentation, I will close the old pull request, because it has been broken for quite a while. (The old one will be closed now) |
The failing test is invalid, it relies on the onerror handler being called if source is not set:
I also did a double check with a running mojarra server, and there also the onerror handler is not called for this case. |
removing an invalid test! (not spec conform and neither does mojarra behave like that)
TCKs pass, however the Tobago people reported an issue with the fileupload for the RC34 of the jsf_ts codebase which needs a fix, so no merge this week, RC33 worked, but I do not want to fork the codebase there. Fixed I will rerun the TCKs now, hopefully for a last time before going into the merge! |
Refixing the fileupload after a report by the Tobag guys.
Note originally in faces 23 Test 1423 was failing due to a race condition between webdriver and js engine execution, this is an issue of the test itself (timing issue, with a race condition between the webdriver and the test code, which is not fixable on framework level, but the test itself needs adaption) Tobago guys also gave the ok... seems like we are set now... I already am in the weekend, so I will merge monday! |
Hi bad news... i got a mild infection, and currently being in bed with fever, so I will leave the honor for the merge to @volosied, @tandraschko or @pnicolucci unless you want to wait until I have recovered (which might be wednesday) |
@werpu i did a small review again and looks good but wednesday is enough, gute besserung :) |
This is mostly a complexity reduction, because instead of 4-5 different target builds (without mapping files back then) we had in the original, we now have only two: production and development, but also we have mapping files. Thats all there is to it. |
lets merge this |
I will second that I know this was a LOT of work. |
the build somehow fails on localhost:
Der Befehl "env" ist entweder falsch geschrieben oder konnte nicht gefunden werden. any idea? |
@tandraschko thanks for the merge, this is a windows build issue, as it seems, which I have not caught upfront: webpack/webpack.js.org#2733 You have to run an npm install first, it wont be there automatically: https://stackoverflow.com/questions/11928013/node-env-is-not-recognized-as-an-internal-or-external-command-operable-comman Another option would be to detect the build os on programmatical level and set the environment vars accordingly. Either way if you cannot figure it out, then I will fix it Wednesday for you. Should not block the CI build which is running on a unixoid environment, but needs to be fixed, feel free to open a bug report and assign it to me. |
@tandraschko could you resolve the issue? Otherwise I will look into it! |
@werpu i didnt had the time |
resolved it with @tandraschko, we can see the issue as closed now. The fix was indeed to use the cross-env package as replacement for the env command. I was not aware of the cross platform issues env in Node has and many people aren´t as it seems. Fix is merged by @tandraschko |
I have to open another pull request on the same branch, because the original one has been showing a merge error for quite some time. The merge is imminent, I just want to run another set of TCKs tests with the latest codebase