Harry, You may be able to speed things up by skipping the minification step during development or test builds by using the -Dminimize=false option. The merging will still be needed as soon as we start to break the js and css files into smaller chunks.
I wonder if maven would be smart enough to skip the merging when no changes are done to the source files. So far, I have not seen this happening. dirk On Mon, Aug 5, 2013 at 6:56 AM, Harry Metske <harry.met...@gmail.com> wrote: > +0.5 > > I have very little knowledge/experience with js and css. I trust what you > say is the right thing to do. > It would be nice to have an option to skip this wro4j step when running > (individual) mvn tests, cause the wro4j step takes quite a bit of time. > > kind regards, > Harry > > > > On 4 August 2013 23:49, Dirk Frederickx <dirk.frederi...@gmail.com> wrote: > > > Hi all, > > > > I recently added WRO4J to the build chain of JSPWIKI. (see > > https://issues.apache.org/jira/browse/JSPWIKI-761 for more details) > > > > The main goal is the introduction of a proper build system for the JS and > > CSS files, allowing to move away from the current monolithic JS and CSS > > files, and break them up in smaller files. > > > > JSPWiki-797 and JSPWIKI-798 are created to track further progress on the > > refactoring of the javascript and stylesheets of JSPWIKI. > > > > > > I'd like to get your feedback/comments for these proposed improvements. > > (preferably in JIRA) If by next friday, there are no objections, I > > consider the proposed way forward accepted. > > > > > > As this change only affects the build system of jspwiki, I assume a > formal > > vote is not necessary. > > > > > > > > Txs, > > dirk > > >
