feat: Enabled resourceChain for the webjars handler

[jonathanmtran]

Checklist

• the individual contributor license agreement is signed
• commit message follows commit guidelines

Description of change

Enabled resourceChain for the webjars handler. This enables webjars-locator to function when present (added to build.gradle overlays/resource-server/build.gradle)

webjar-locator allows us to drop the version when sourcing dependencies such as web components
https://www.webjars.org/documentation#springboot

I got the change to make from https://stackoverflow.com/questions/44200423/webjars-locator-doesnt-work-with-xml-based-spring-mvc-4-2-x-configuration

Example Use Case

<script src="https://unpkg.com/vue@2.5.16"></script>
<script type="text/javascript" src="/resource-server/webjars/uportal__content-carousel/dist/content-carousel.js"></script>

[ChristianMurphy]

Neat! Thanks @jonathanmtran!

[drewwills]

This is a desirable feature.

Does it work? I had a lot of problems with it in FBMS.

I see this warning in the docs...

Following the Spring MVC instructions in a Spring Boot project will result in disabling the static content mapping configured by Spring Boot.

What does it mean? (I don't follow.)

[jonathanmtran]

Does it work? I had a lot of problems with it in FBMS.

So far so good. It could benefit from additional testing

I got the change to make from https://stackoverflow.com/questions/44200423/webjars-locator-doesnt-work-with-xml-based-spring-mvc-4-2-x-configuration

[drewwills]

👍

[drewwills]

@jonathanmtran, @ChristianMurphy, @jgribonvald, @cousquer...

Can anyone think of a good reason not to add webjars-locator directly to resource-server-webapp? So we will always have it?

I'm inclined to do that.

[drewwills]

FYI -- I just tested this change locally... works great! 👍

[drewwills]

@jonathanmtran et al.,

I'm going to go ahead and bake the webjars-locator dependency into resource-server-webapp.

The benefits of having it are pretty clear, and AFAIK there aren't any downsides...

• You can't easily convince a build system to package multiple versions of the same dependency; you'd probably have to do that by hand.
• And even if you did that -- and actually wanted that -- you can still use the full, version specific path if you want to (AFAIK).

[ChristianMurphy]

Sounds good, merge away

[cousquer]

Sounds good to me also. Great idea @drewwills !

[jgribonvald]

Yes i'm for the merge too !