Yes you‘re right. We talked in the MVC call about that and decided the web.xml fix should be enough.
Von meinem iPhone gesendet Am 17.02.2022 um 16:08 schrieb Christian Kaltepoth <christian@xxxxxxxxxxxx>:
I'm not completely sure if we should really remove Nashorn support in a patch release to be honest. However, I'm not -1 for the idea. Sure, sounds good to me
Ivar
Hi all,
maybe we could add the removal of the nashorn engine too, as this is a JRE related topic and is therefore relevant for Krazo 1.1.0.
Best regards,
Tobias Von meinem iPhone gesendet Hi all,
I was wondering if we should plan a bugfix release for Krazo 1.1.0, which is the latest version for the "javax.mvc" version of the spec. Especially, this seems to cause issues for users:
Maybe we could integrate other fixes as well? Any ideas?
I already cherry-picked the fix for #265 to the "release-1.1.0" branch in our repo. So basically we would be ready for a 1.1.1 release if we don't want to integrate other fixes as well.
_______________________________________________krazo-dev mailing listkrazo-dev@xxxxxxxxxxxTo unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/krazo-dev
_______________________________________________
krazo-dev mailing list
krazo-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/krazo-dev
--
Ivar Grimstad Jakarta EE Developer Advocate | Eclipse Foundation
Eclipse Foundation - Community. Code. Collaboration.
_______________________________________________
krazo-dev mailing list
krazo-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/krazo-dev
--
_______________________________________________krazo-dev mailing listkrazo-dev@xxxxxxxxxxxTo unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/krazo-dev
|