There is no specific test plan for this, just moving a dependency from one place to another. If you are able to work with samigo, msgcntr or signup the patch is working right, so feel free to mark it as verified and keep going.

@Juanjo Meroño how would you go about testing this? Do you have a test plan?

Is this something that can be verified by QA? 

Reviewed by CoreTeam at 12/4/2018 meeting.

After a brief discussion with @Miguel Pellicer we thought that this library, used in jsf tools, should be moved to tool scope to be able to change its version independently on each tool in the future.

Right now (Sakai 19/20) some tools are still using jsf 1.1 but the library has to be updated and happily no problems seems to be faced so far. I mean that chat and samigo are using jsf 2 that requires jstl 1.2 but syllabus and podcasts are using jsf 1 and forced to use jstl 1.2 also, and it works, but maybe we won't be so lucky in the future.

Having this library in global scope would force a massive migration of jsf tools in the future instead of migrate them one by one with several efforts. But you did it right the core team call is the perfect place to discuss about this issue. 👍 Thanks @Laura Gekeler !!