This is worth explaining.  The context root of a webapp can be changed.  So static resources inside the webapp can change.  Unless you use a URL re-writer like Tuckey, which I prefer to not do, the resource location will change.  By using JSTL's <c:url> tag, it enabled me to use the fingerprint plugin for static resources with a changing context root.  Another method would be to use ${pageContext.request.contextPath}, which should arguably also be valid also.

I think static resources should be valid inside the webapp with a changing context root.  This was one way to do it in a way that didn't conflict with the rest of the fingerprint plugin's design.

I put an example of this in the JUnit tests because it was a design goal of mine.  So this could be handled this way in the JSP page:
<c:url value="/resources/css/style.css" var="styleUrl"  scope="page" />
<link rel="stylesheet" href="${styleUrl}" />

This will then allow a changing context root and fingerprint matching of the static resource.