Hi all,

this might concern a few people migrating to 1.0 under certain
circumstances, namely if they use the "compile-source" or "compile-dist"
config keys in their config.json. If you never did that, this one is not
for you.

Contrary to the initial 1.0 release notes, which just deprecated the old
compile-source/compile-dist keys [1], there are case where you have to do
an additional step in the migration process concerning these. If you have
extended or overridden one of the standard build jobs "source-script" or
"build-script", using the old compile keys, you need to migrate them to
the new keys. E.g. this is the case if you have a job like this in your
config.json

  "build-script" : {  // overriding the standard build-script job
    "compile-dist" : {
      ...
    }
  }

or like this

  "mybuild-script" : {
    "extend" : [ "build-script" ...],  // extending standard build-script
    "compile-dist" : { ... },
    ...
  }

(and similarly for "source-script" and "compile-source"). Then see [2] for
migration details. Failing to do so would usually result in error-free
build runs by the generator, but not all build options being applied as
expected (e.g. not all locales being processed, or customized optimization
settings not being applied, asf.). The consequences might only show in the
running application.

The additional step is not necessary if you use the old
compile-source/compile-dist keys *without* making references to the
standard build jobs, i.e. where you filled in all the compilation settings
on your own. In these cases the old keys continue to work as expected
(though migrating them wouldn't hurt either). I have adapted the release
notes and the general migration guide [3] accordingly.

Sorry for the hassle.

Thomas

[1] http://qooxdoo.org/about/release_notes/1.0#tooling
[2] http://qooxdoo.org/documentation/1.0/migration_config
[3] http://qooxdoo.org/documentation/1.0/migration_guide


------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to