Re: [wro4j] Disabling JS file concatenation/consolidation when running wro4j Maven at build time

[Julien Wajsberg]

Hi,

What is exactly your concern ? You want to be able to debug the unminified file ? Or you want to make the build faster ?

For the first one, we created wro4j-taglib : https://github.com/Orange-OpenSource/wro4j-taglib

This makes it easier to serve the unminified files instead of the optimized files.

To make the build faster, by carefully chosing the maven goal bound for wro4j, we managed to avoid optimizing with the maven eclipse plugin, which was actually quite painful because it was slow.

Regards,

--

Julien

On 18 March 2013 16:15, Chris Pearce <chris_...@hotmail.com> wrote:

I use the Maven Plugin for minimization, JSHint, CSSLint, etc. at build time and find the wro4j to an invaluable tool.

However, I'd like to disable the combining/concatenating of the JS files that occurs as part of the Maven build cycle. Currently I have a workaround of creating a group for each individual JS file. Whilst this works, it adds a fair bit of overhead as every new JS file added to the project needs to be added to the wro.xml file.

Are there any plans to provide support for the scenario I have mentioned above?

If not, any guidance on how I could extend the capabilities of wro4j to prevent file combining/concatenation when using Maven (rather than at runtime) would be greatly appreciated.

Thanks in advance

Chris

--
You received this message because you are subscribed to the Google Groups "wro4j" group.
To unsubscribe from this group and stop receiving emails from it, send an email to wro4j+un...@googlegroups.com.
To post to this group, send email to wr...@googlegroups.com.
Visit this group at http://groups.google.com/group/wro4j?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Chris Pearce]

I'm wanting to build the solution (with minimized JavaScript files) but preserve the JavaScript file structure rather than have the files combined into a single JavaScript file.

n.b. I'm using WRO4J for builds not at runtime.

[Alex Objelean]

Hi Chris,

if you need a build time solution, there is an open issue which will be implemented at some point in the future (contributions are encouraged, including use case description and defining detailed acceptance criteria).

For the runtime solution, you can extend the AbstractProcessorsFilter which is designed for on the fly processing of any given resource.

Let me know if you have any questions.

Cheers, 

Alex