Add support incremental for incremental builds

[GoogleCodeExporter]

While importing the wro4j-demo project to test m2e-wro4j, I realized wro4j can 
take a veeery long time to run (several seconds), every time I save the pom.xml 
or change a css or js resource in Eclipse.

It might be beneficial if the wro4j maven plugin (and wro4j as well 
incidentally) could run resource optimization only on changed resources. It may 
very well not make any sense since resources are aggregated from several files.

Anyway, in order to integrate better with IDEs, you should use the BuildContext 
from the plexus build API (see 
http://wiki.eclipse.org/M2E_compatible_maven_plugins).

Just saying :-)

Original issue reported on code.google.com by fbri...@gmail.com on 23 Jan 2012 at 10:32

[GoogleCodeExporter]

Thanks for suggestion. Will have a look at that. Any other suggestions or 
patches are welcome.

Original comment by alex.obj...@gmail.com on 24 Jan 2012 at 7:35

• Changed state: Accepted
• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

There are a couple of issues which will be fixed in next release which 
indirectly will solve the problem related to this issue:

1) There will be a LessCssProcessor which will use node-js v8 engine if it is 
detected and supported
2) The maven plugin will process groups in parallel. Thus build will be 
performed much faster.

Given that, I'm wondering if this issue is not obsolete? What do you think?

Original comment by alex.obj...@gmail.com on 15 Sep 2012 at 10:53

[GoogleCodeExporter]

What we need is a way to only process the groups impacted by changed files. If 
your implementation fixes that, then you can close this issue. 

Original comment by fbri...@gmail.com on 16 Sep 2012 at 4:16