Success! Looks like we've fixed this one. According to our records the fix was applied for
a recent build.
<feature logger> doesn't work
Ext version tested:
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:
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:
Forgot to mention this was Sencha Cmd 22.214.171.124. 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.)
If I run "sencha -d app build production", the output includes:
This is despite the fact that I have buildOptions.logger = true in app.json. I also tried adding "app.logger=true" and "logger=true" to sencha.cfg, but it still says "logger:no".
[DBG] running compiler with options : '[...]logger:no[...]
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:
around line 255 or so.
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.
Ah, thanks. I was looking for something like that (it was actually line 449).
Any updates to this process in Sencha Cmd 3.0.1? It looks like that value is still hard-coded.
Apologies. Apparently this never got escalated to our tracker - doing so now.
It looks like adding the following to your sencha.cfg file fixes this:
More specifically, this could be done in any level of the Sencha Cmd sencha.cfg files (app, workspace, etc)
Tested using Cmd 126.96.36.1994
Great! Sencha Cmd 188.8.131.524 requires Sencha Touch 2.2, right? Or can I use it with 2.1?
It is backward compatible... though you should upgrade your app too