6 Nov 2012 8:58 AM #1
<feature logger> doesn't work
Ext version tested:
- Sencha Touch 2.1 final
Browser versions tested against:
DOCTYPE tested against:
- Can't require or extend classes like Ext.log.writer.Remote, when they're wrapped in "//<feature logger>" comments..
Steps to reproduce the problem:
- Use Sencha Cmd to generate an app.
- Add 'Ext.log.writer.Remote' to the Ext.application call's "requires" config.
- In app.json, set "logger": true in "buildOptions".
- Run "sencha app build production".
The result that was expected:
- Builds correctly.
The result that occurs instead:
[INF] Processing instantiation refereces to classes and aliases [INF] Processing source dependencies [ERR] Failed to find file for Ext.log.writer.Remote required by /Users/jacobweber/Test/app.js [ERR] BUILD FAILED
Screenshot or Video:
See this URL for live test case: N/A
Debugging already done:
- Removing the <feature> tags in the Sencha source fixes the problem. Changing the value of "logger" in "buildOptions" doesn't seem to make a difference.
Additional CSS used:
- only default ext-all.css
- Mac OS 10.8.2
8 Nov 2012 11:04 AM #2
Forgot to mention this was Sencha Cmd 184.108.40.206. I'm not sure if this should go here or in the Sencha Touch bugs forum.
(It seems like this Sencha Cmd forum shouldn't be grouped under Ext JS, since it applies to Sencha Touch too.)
19 Nov 2012 9:49 AM #3
If I run "sencha -d app build production", the output includes:
[DBG] running compiler with options : '[...]logger:no[...]
19 Nov 2012 3:01 PM #4
We plan to further normalize the app build process between ext and touch so that such things are configurable on both... but at the current time, the compiler options setting is hard-coded in this script:
Obviously changes to this file will need to be performed any time you upgrade Cmd but it can be hacked to get what you need for now.
19 Nov 2012 3:19 PM #5
Ah, thanks. I was looking for something like that (it was actually line 449).
22 Dec 2012 12:57 PM #6
Any updates to this process in Sencha Cmd 3.0.1? It looks like that value is still hard-coded.
22 Dec 2012 2:44 PM #7
Apologies. Apparently this never got escalated to our tracker - doing so now.
6 May 2013 9:36 AM #8
It looks like adding the following to your sencha.cfg file fixes this:
6 May 2013 10:04 AM #9
Great! Sencha Cmd 220.127.116.114 requires Sencha Touch 2.2, right? Or can I use it with 2.1?
6 May 2013 10:12 AM #10
It is backward compatible... though you should upgrade your app too