On my current project, I've used YUI Compressor using the following Maven plugin: http://alchim.sourceforge.net/yuicompressor-maven-plugin/overview.html
It worked quite nice (compression and aggregation). We might be able to use this plugin for MyFaces too? /JK 2009/8/4 Werner Punz <[email protected]>: > Hello again, since I am back from my vacation I want to raise this topic > again since no one really answered the last two times but it is a pressing > matter. > > Currently we have the javascripts in good condition and basically they are > ready to be used, but we still have one issue which is not really > satisfiable in my opinion, that is the build process. > > We currently have following situation, we are very modular in our approach > with the codebase following the one class one file convention. > The javascript files are compressed and bundled by the standard maven > javascript plugin, which works but is not enabled in the build process and > should be enabled the next weeks. > > But there is one thing unsatisfying about this approach. > The standard javascript plugin is declared alpha quality and the build > process has been broken due to changes in the codebase at least once because > of it. > (Note the entire compression is stable because it uses the YUI compression > engine internally, which is supposed to be the best out > there currently) > > We also have a javascript plugin which I am not sure what it does exactly (i > think the same compression and concatenation) > but it bombed out on me with an NPE when I tried to enable it, I have not > had time to investigate it. > > My current question is, which one to use > > a) Use the maven javascript plugin and live with occasional build hickups > until the plugin is finished > > b) Fix our current plugin to a usable state so that it works within the > scope of our build process > > > If b) is the preferred solution I will start to fix the plugin so that we > can change it sometime this month! > > Also another thing is how can we integrate selenium, I have a bunch of > selenium tests which currently trigger against the RI and the myfaces > scripts, but as I see it you cannot use them headless. Is there a > possibility to integrate selenium in our build process or shall we simply > drop them as subproject not triggered by the build as soon as our codebase > works to a satisfyable degree. (I do not want to check in a > RI dependency into our codebase) > > > > Werner > >
