Hi, welcome to qooxdoo. :-)
On Thu, 2009-09-03 at 16:47 +0200, [email protected] wrote: > I started with qooxdoo about one week ago, out of curiosity. I finished one > simple qooxdoo class, now I'd add some unit tests to it. > > However, neither generate.py test nor generate.py source-all run through. > Here's the output from generate.py source-all: > > $ ./generate.py source-all > > ============================================================================ > INITIALIZING: MyApp > ============================================================================ > >>> Configuration: config.json > >>> Jobs: source-all > >>> Resolving config includes... > >>> Resolving jobs... > >>> Resolving macros... > >>> Resolving libs/manifests... > > ============================================================================ > EXECUTING: SOURCE-ALL::SOURCE-ALL-SCRIPT > ============================================================================ > >>> Scanning libraries... > - Scanning /cygdrive/d/downloads/qooxdoo/qooxdoo-0.8.2-sdk/framework... > - Scanning /cygdrive/d/workFJ/JSWork/MyApp... > - Excludes may break code! > >>> Resolving dependencies... > !!! Dependencies resolving failed for myapp.model.NumericAttribute with: > Could not resolve dependencies of class: myapp.model.NumericAttribute > Could not resolve dependencies of class: qx.core.Object > Could not resolve dependencies of class: qx.core.Property > Could not resolve dependencies of class: qx.Class > Could not resolve dependencies of class: qx.core.Setting > Could not resolve dependencies of class: qx.Bootstrap > Could not resolve dependencies of class: qx.lang.Core > Could not find class to fulfil dependency: qx.lang.Core > > Since the messages refer to something like a classpath problem in Java, I > suppose the problem is not related to code. > > config.json contains this line: > > "QOOXDOO_PATH" : "/cygdrive/d/downloads/qooxdoo/qooxdoo-0.8.2-sdk", > > where I only changed the value - create-application.by placed a path > with lots of /../ in it, I just replaced it with an absolute path. So the auto-generated QOOXDOO_PATH worked, only your manually entered absolute path didn't? If yes, wouldn't you just like to keep the generated path (for the moment)? To trigger detailed debugging output, you could also invoke $ ./generate.py -verbose source-all but I doubt it will help much here. What did the generated path look like exactly? What about using a relative path to your qooxdoo folder instead of your absolute path, i.e. ../../../downloads/qooxdoo/qooxdoo-0.8.2-sdk/framework HTH, Andreas ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
