[Announce] wro4j-1.4.8 released!

[Alex Objelean]

This release contains a fix for 15 issues. Most of them are bug fixes. There are also several new features, most notable being: automatic resource change detection and cache invalidation

The complete list of fixed issues can be found here (or here: http://code.google.com/p/wro4j/wiki/ReleaseNotes). 

Thanks to all contributors. 

Cheers,

Alex

[Julien Wajsberg]

On 9 August 2012 12:08, Alex Objelean <alex.o...@gmail.com> wrote:
> There are also several new features, most notable being: automatic resource change
> detection and cache invalidation

That is awesome.

Thanks
--
Julien

[Alex Objelean]

Hi all,

a new bug has been reported on 1.4.8 release which breaks the CssImport processor in some situations: http://code.google.com/p/wro4j/issues/detail?id=507

The issue has been fixed already in the main development branch (1.4.x) and will be released as part of 1.4.9 version.

If this affects your code, but you still would like to upgrade, you have the following options:

1)  Remove the css comments which causes the problem (see http://code.google.com/p/wro4j/issues/detail?id=507 for more details)

2) Use a custom CssImport processor which should have just a single line changed:

    on line #68 instead of 

private static final String REGEX_IMPORT_FROM_COMMENTS = WroUtil.loadRegexpWithKey("cssImportFromComments");

use

private static final String REGEX_IMPORT_FROM_COMMENTS = "(?:/\\*(?:[^*]|(?:\\*+[^*/]))*+\\*+/)|(?://.*)";

The problem was caused by a small issue with regular expression which is read from regexp.properties file. The patched version should fix that. 

Of course, don't forget to use your custom CssImport processor instead of the old one. Read more about how to do that on this page: http://code.google.com/p/wro4j/wiki/RegisterCustomProcessors

Thanks,

Alex