8 Jan 2013 10:50 AM #1
Sencha Cmd 220.127.116.11 incorrectly setting extjs version during ant build
For extjs version 4.1.3, I'm trying to apply a patch to the extjs code using sencha ant build. This seems to work fine, except for that the version number gets set incorrectly.
Before running ant build, the version in the code = '18.104.22.1688', but after the build the version = '4.1.2'. Perhaps this is hard coded in someplace? I *think* the rest of the build process worked ok since the diff between the two files shows changes back and forth, but I can't be sure.
Anyone else seen this?
9 Jan 2013 5:06 AM #2
9 Jan 2013 8:23 AM #3
also not working in 22.214.171.1248
made sure I'm using the new one:
../../Sencha/Cmd/126.96.36.1998/sencha ant build
28 Jan 2013 7:04 AM #4
I think maybe the Ext Core files should be doing this:
21 Feb 2013 10:52 AM #5
As a n00b with Sencha Cmd I got caught by this bug and wasted a couple of hours tracking down the wrong version... Cmd 188.8.131.528 and a freshly dowloaded 4.1.3 ExtJS... sigh!
12 Mar 2013 7:32 AM #6
Been waiting for Sencha Care (ticket #11145) to care about this but with no luck so far...
I produced a screencast of this, could someone please tell me what I am doing wrong?
Sencha Cmd 184.108.40.2068
16 Mar 2013 12:23 AM #7
The problem here is that Cmd does not stamp version numbers on the src files and the bug is actually in those versions of Ext JS. The Ext JS build process stamps the version number in to the builds (e.g., "ext-all-debug.js") but it did not stamp the contents of src.
I believe this has been fixed in 4.2 SDK's but 4.1.1 to 4.1.3 simply did not stamp those two places properly. The easy fix is to correct them in the src files and then future rebuilds of the SDK will just concat them in.
At least I assume you are rebuilding the Ext JS SDK itself using "sencha ant build" from the root of the SDK. If not, don't hesitate to set me straight.
16 Mar 2013 12:29 AM #8
Sorry- I just noticed the video link you posted. The bug is the same as I described just the target of the build is not the SDK.
Since Cmd does not stamp versions, the only real fix is to the src files where "4.1.2" resides. Or some special build-step in your app that corrects for this using those SDK's.
Do you see this in 4.2 (if you've had a chance to try it)?