I'm having trouble understanding the difference between classpath vs.
context assets -- when is it better to use one or the other? Right now I've
been putting Javascript and CSS under src/main/webapp/ , and referencing it
old-school using <script src="foo.js" type="text/javascript" ></script> but
am learning about the new @IncludeJavaScriptLibrary annotation. It appears
to use classpath assets though, and if I understand it correctly, expects
files to be in src/main/resources. Another advantage of classpath assets
appears to be versioning for cache-busting (although it looks like 5.1 will
include this for context assets too?). Should I be putting my JS/CSS/static
images in src/main/resources, packaged with .tml files?

Anyway, any sort of clarification would be appreciated.

Thanks,
Jason

Reply via email to