issue with the GeoExt Build while migrating from 3.X to 4.X
We are migrating our application from GeoExt 0.7 to 2.0 and ExtJS to 3.3.0 to 4.1.0.
We downloaded the 2.1.0 from the Sencha link however I see there is no build folder available so copied it from the 0.7 folder which was already with us.
When we try to build 2.0 we found that its not working at all. When we compared tGeoExt 0.7 and 2.0 we come to know that the directory stucture is totally changed and may be becouse of that the old build script is not working with the newer version.
It would be great help if any body has any idea abt the new build script for the new frame work that is GeoExt 2.0
We are still trying to find the fix as problem is not resolved yet.
However we checked that the GeoExt 2.0 build script is working with ExtJS 3.3.0 but when we changed the reference to ExtJs 4.1.0 it doesn't work.
We are getting below error.
Traceback (most recent call last):
File "/usr/bin/jsbuild", line 7, in ?
File "<string>", line 2, in build
File "/usr/lib/python2.4/site-packages/JSTools-0.1b-py2.4.egg/jstools/utils.py", line 20, in _caller
return func(args, options, optparser)
File "/usr/lib/python2.4/site-packages/JSTools-0.1b-py2.4.egg/jstools/build.py", line 53, in build
out = merger.run(uncompressed=options.uncompress, single=options.single_file)
File "/usr/lib/python2.4/site-packages/JSTools-0.1b-py2.4.egg/jstools/merge.py", line 149, in run
merged = self.merge(cfg)
File "/usr/lib/python2.4/site-packages/JSTools-0.1b-py2.4.egg/jstools/merge.py", line 77, in merge
files[path] = self.make_sourcefile(sourcedir, path, exclude)
File "/usr/lib/python2.4/site-packages/JSTools-0.1b-py2.4.egg/jstools/merge.py", line 55, in make_sourcefile
return SourceFile(sourcedir, filepath, exclude)
File "/usr/lib/python2.4/site-packages/JSTools-0.1b-py2.4.egg/jstools/merge.py", line 183, in __init__
self.source = open(os.path.join(sourcedir, filepath), "U").read()
IOError: [Errno 2] No such file or directory: '../lib/OpenLayers/Layer/WMS.js'
I appreciate your information, but I would still like the result of you asking GeoExt about this error since they are responsible for this product.
From your original post, I gather the build is where it is falling apart, and it seems to be related to loading 3rd party code from the list of error files. Have you tried creating a simple build project and see of it works, then slowly adding items that exist in your build file to see what is causing this?
Hopefully someone with experience with this product can jump in and help.