On 08/17/2011 04:00 PM, omrihar wrote: > Hi, > > Thanks for the help. I did do that before (I defined the cache directory to > somewhere which is accessible to the web server). > > I found the problem, which was that while the cache folder was defined by > "cache" : "./cache", the uri has to be defined as "uri" : > "../cache/downloads/..." for some reason.
Look, if you follow Marc's link you will find there is no "cache" key that takes a string value. Rather, "cache" holds a map. The CACHE macro, on the other hand, takes a single path as argument. So if you want to modify the cache path(s) you have two options: (1) In your build *job*, add the 'cache' config key and provide it with a *map* value (s. Marc's link). This allows you to specify the compile and download cache paths individually. (2) In your *let* section, add a CACHE macro with a *string* (path) value. As you can see from the 'cache' documentation, the 'download' folder will then be a subdirectory of the path given with CACHE. In both cases, the generator will create correct URIs to a downloaded contribution if you use the *file://* protocol. When running the source version of the app through a web server, the concerns discussed previously apply. And yes, one possible fix for any library (including downloaded contrib libraries) is to adjust the library's 'uri' config parameter. See the last paragraph of [1] (just above "contrib:// URIs and Internet Access") for a treatment. T. [1] http://manual.qooxdoo.org/1.5.x/pages/tool/generator_config_articles.html#contrib-libraries ------------------------------------------------------------------------------ Get a FREE DOWNLOAD! and learn more about uberSVN rich system, user administration capabilities and model configuration. Take the hassle out of deploying and managing Subversion and the tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2 _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
