>-----Original Message----- >From: Sean Cooper [mailto:[email protected]] >Sent: Friday, March 30, 2012 11:43 AM >To: [email protected] >Subject: Re: [DISCUSS] wro4j for static file optimizations > >On Fri, Mar 30, 2012 at 11:40 AM, Carlucci, Tony <[email protected]>wrote: > >> Hello Rave Devs, >> >> In my research for RAVE-518[1] (JavaScript improvements) I came across a >> tool called wro4j[2] which allows for either build-time or run-time >> compression and minification of static resources like javascript, css, etc. >> When I set out originally to work on this task I had envisioned doing all >> of the optimization at build-time, but I wanted to open it up to the >> community to see if: >> >> >> a) Someone has used wro4j in the past and can comment on pros/cons? >> >> b) Would we want to do resource optimization at build-time (via >> maven) or run-time? >> >> >Run time? Like at every page load? Or would the compression and >minification happen when the application loads? >-Sean
wro4j has a whole caching strategy (which can be customized) for the run-time option. I've been looking over the feature list and it is pretty robust. Performs tasks like gzip compression and supports CSS Meta Frameworks like LessCss. Tony > >> Thanks, Tony >> >> [1] https://issues.apache.org/jira/browse/RAVE-518 >> [2] http://code.google.com/p/wro4j/ >> >> >>
