jamesward
commented
10 years ago The webjars-locator library already parses the version / path info to make this easy. I'd rather stick with using that instead of adding more complexity to the builds. Feel free to suggest or contribute any improvements to webjars-locator.
When consuming webjars in a templating engine like thymeleaf, you have to know the full path to the javascript and CSS files.
The specific version information is already in the pom, so repeating yourself in all the template files (e.g. ) is duplicate work at best and a potential error source at worst. If each webjar would provide an (automatically generated and compiled) java constants class, this x.y.z version information could be inferred automatically in the templates (see the "T" operator in Spring EL at http://doanduyhai.wordpress.com/2012/04/14/spring-mvc-part-iv-thymeleaf-advanced-usage/ )