The "settings" key has been deprecated with 1.4 [1] (you must have ignored the deprecation warnings all along), and support for it has been removed with 1.5. Replace "settings" with "environment" in your config, and you should be all set.
T. [1] http://qooxdoo.org/about/release_notes/1.4#tooling > In my config.json I have: > > "jobs" : > { > "common" > { > "settings" : > { > "my.key" : "stringValue" > } > } > } > > Under 1.4.2 I was able to get the "stringValue" like this: > > var a = qx.core.Environment.get("my.key"); > > After migrating to 1.5 I got a warning in firebug: > > "my.key is not a valid key..." > > I've tried to find out what changed, but could't find it. > > Could somebody help me with this? > > > > -- > View this message in context: > http://qooxdoo.678.n2.nabble.com/problem-with-qx-core-Environment-get-under-qooxdoo-1-5-tp6615622p6615622.html > Sent from the qooxdoo mailing list archive at Nabble.com. > > ------------------------------------------------------------------------------ > Magic Quadrant for Content-Aware Data Loss Prevention > Research study explores the data loss prevention market. Includes in-depth > analysis on the changes within the DLP market, and the criteria used to > evaluate the strengths and weaknesses of these DLP solutions. > http://www.accelacomm.com/jaw/sfnl/114/51385063/ > _______________________________________________ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > > > ------------------------------------------------------------------------------ Magic Quadrant for Content-Aware Data Loss Prevention Research study explores the data loss prevention market. Includes in-depth analysis on the changes within the DLP market, and the criteria used to evaluate the strengths and weaknesses of these DLP solutions. http://www.accelacomm.com/jaw/sfnl/114/51385063/ _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
