Skip to main content

Debug override not taking into account debugonly, debugnever

  2 posts   Feedicon  
Replies: 1 - Last Post: February 25, 2012 16:26
by: icefox
showing 1 - 2 of 2
Posted: February 24, 2012 12:40 by michael.ho
Hi,

First, I want to say, I have been using Jawr for a few years now and I love what you've done with the project. Great work!

The issue I am having (in v3.3.3) is the following (using ExtJS as an example):

SETTINGS:
---------------
jawr.debug.on=false
jawr.debug.overrideKey=debug

# Our global lib bundle
jawr.js.bundle.lib.id=/bundles/lib.js
jawr.js.bundle.lib.global=true
jawr.js.bundle.lib.composite=true
jawr.js.bundle.lib.child.names=extall,extalldebug

# Use ext-all when debug is off, no minification
jawr.js.bundle.extall.mappings=/js/lib/ext-all.js
jawr.js.bundle.extall.bundlepostprocessors=none
jawr.js.bundle.extall.debugnever=true

# Use ext-all-debug when debug is on, no minification
jawr.js.bundle.extalldebug.mappings=/js/lib/ext-all-debug.js
jawr.js.bundle.extalldebug.bundlepostprocessors=none
jawr.js.bundle.extalldebug.debugonly=true

ISSUE:
----------
1. Hit webapp with ?overrideKey=debug
2. Bundles are exploded properly, but you still get extall bundle vs extalldebug bundle.
3. The only way to get extalldebug is to deploy with jawr.debug.on=true

Is this expected behavior, and/or am I doing something incorrect with my configuration?

Thanks!
-Mike
Posted: February 25, 2012 16:26 by icefox
Hi Michael,

This seems to be a bug.

I'll create a JIRA for this one.
Thanks for reporting it.

Cheers;
Replies: 1 - Last Post: February 25, 2012 16:26
by: icefox
 
 
Close
loading
Please Confirm
Close