PDA

View Full Version : [FIXED] building from SVN fails



neongrau
27 Oct 2011, 1:19 AM
trying to build the sdk (on OSX Lion) spits alot of warnings, a syntax error, finishes with broken result.


./build.sh out sdk


[NOTICE][Parser.Statement.factory] Statement type 'feature' is currently not supported, ignored
* Compress and obfuscate ext.js...
sh: -c: line 0: syntax error near unexpected token `('
sh: -c: line 0: `java -jar ../jsbuilder/ycompressor/ycompressor.jar --type js -o /Users/neongrau/ext-4.0.x (branch)/extjs/build/out/ext.js /Users/neongrau/ext-4.0.x (branch)/extjs/build/out/ext.js-temp-915906914114.8816'


neonmac:~/ext-4.0.x (branch)/extjs/build neongrau$ java -version
java version "1.6.0_26"
Java(TM) SE Runtime Environment (build 1.6.0_26-b03-383-11A511)
Java HotSpot(TM) 64-Bit Server VM (build 20.1-b02-383, mixed mode)

what is causing the problem here?

neongrau
27 Oct 2011, 2:48 AM
ok, one part of the problem is solved by using a more simple directory name since the buidl script fails to quote the dir properly.


but still no change in the broken result



[NOTICE][Parser.Statement.factory] Statement type 'feature' is currently not supported, ignored
* Compress and obfuscate builds/ext-all-sandbox.js...

[ERROR] 100921:4:syntax error

[ERROR] 100924:2:missing } after property list

[ERROR] 1:0:Compilation produced 2 syntax errors.
org.mozilla.javascript.EvaluatorException: Compilation produced 2 syntax errors.
at com.yahoo.platform.yui.compressor.YUICompressor$1.runtimeError(YUICompressor.java:135)
at org.mozilla.javascript.Parser.parse(Parser.java:410)
at org.mozilla.javascript.Parser.parse(Parser.java:355)
at com.yahoo.platform.yui.compressor.JavaScriptCompressor.parse(JavaScriptCompressor.java:312)
at com.yahoo.platform.yui.compressor.JavaScriptCompressor.<init>(JavaScriptCompressor.java:533)
at com.yahoo.platform.yui.compressor.YUICompressor.main(YUICompressor.java:112)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.yahoo.platform.yui.compressor.Bootstrap.main(Bootstrap.java:20)

Creating the "Foundation Dev" target as "builds/ext-foundation-dev.js"
- 1 package(s) included in this target.
+ pkgs/foundation.js
* Parse builds/ext-foundation-dev.js with options:
- debug: true
- debugLevel: 1
[NOTICE][Parser.Statement.factory] Statement type 'feature' is currently not supported, ignored

jsakalos
27 Oct 2011, 11:10 AM
Couldn't it be java version problem? Can you test the same on another system? (I'm also on Lion...)

neongrau
28 Oct 2011, 12:33 AM
tried on a collegues machine,

seems like exactly the same java version


java version "1.6.0_26"
Java(TM) SE Runtime Environment (build 1.6.0_26-b03-383-11A511)
Java HotSpot(TM) 64-Bit Server VM (build 20.1-b02-383, mixed mode)

and also exactly the same errors and broken result.

broken as in ext-all.js doesn't get minified and lots of stuff left inside that looks like jdoc comments

jsakalos
28 Oct 2011, 11:52 AM
I'm going to try myself - I have the same java version - but first I need to checkout the svn so I need to refresh my credentials. Will let you know soon my findings.

Actuarybrad
30 Oct 2011, 3:00 PM
Any findings?

Same error on Windows 7 64bit.

jsakalos
31 Oct 2011, 2:32 AM
I've tried to build Ext from svn following instructions from support page. From the checkout directory I run


extjs/build/build.sh deploy sdk


The build process does spits out some errors but doesn't stop and deploy directory seems to contain the relevant files of reasonable sizes. The errors are yui compressor related and the output files are not minified.

So I tried to download yui compressor from yahoo but both 2.4.2 and 2.4.6 produce the same errors.

I cannot say if it is the compressor problem or the errors are elsewhere.

I'm moving this thread to Bugs for developers to fix the issue.

mitchellsimoens
31 Oct 2011, 12:12 PM
I have pushed this into our bug tracker... not sure what is going wrong here but it could very well be in the translation of Git -> SVN

neongrau
15 Nov 2011, 8:04 AM
could it be that there is noone actively working on the 4.0.x branch?

build process is broken and no commits since 20th Oct.

do i need to switch to 4.1.x branch ?

mitchellsimoens
15 Nov 2011, 8:18 AM
All development is on 4.1 now