Open alanmosely opened 10 years ago
Sorry for the late response. I've been on holiday the last weeks.
I don't have any suggestion on how to suppress the warnings. This seems like an issue that is not directly linked to the plugin.
Well there are two things here:
I haven't tested it but you should be able to exclude certain files with grails.resources.googleclosurecompiler.exludes = ['**/*.min.js', 'filetoskip.js']
in your config.
See: http://grails-plugins.github.io/grails-resources/guide/6.%20Creating%20custom%20mappers.html#6.4%20Processing%20only%20the%20right%20types%20of%20files for more info.
Unfortunately that doesn't work, I tried both:
grails.resources.googleclosurecompiler.exludes
grails.resources.mappers.googleclosurecompiler.exludes
for me works in this way
grails.resources.mappers.googleclosurecompiler.excludes = ['**/*.min.js', '**/jquery.touchSwipe.js']
Hi, thanks for the excellent plugin, we are currently facing two issues that are dirtying our production logs on startup.
The first issue is that the plugin is scanning some js from various grails resources/plugins and I don't see how we can exclude them, for example:
The second issue is that although we can surpress these warnings when in dev using: log4j = { error 'com.google.javascript.jscomp', 'org.grails.plugin.resource.mapper.googleclosurecompiler' }
When building a prod war and specifying
grails.logging.jul.usebridge = false
(for performance reasons) the working log4j config above seems to be ignored and I've found no way of surpressing the irrelevant warnings that are shown whenever our prod webapp is started up.