is it possible to have Wicket manage resources (.css and .js) outside of the classpath, so that we can leverage all the great dev/prod things that Wicket does with resources served from within the classpath?
We typically put our resources at the root of the context: /assets/css /assets/js /assets/images /WEB-INF/.... This way we can reference images from within our style sheets using 'background:url(../images/logo.png);' If Wicket were to serve these resources (I guess we would have to move the assets down a level so they were brought in to the accessible classpath of the Wicket app), can we manage such context sensitive references within CSS files that are being managed by Wicket? We're using 6.x N
