Release Notes / Version 10.2107
Table Of ContentsFor 2107, the CMCC 10 long-term service release (LTS), the Studio Client Jangaroo tooling has been updated to a new minor version, changing the version(s) from 4.0 to 4.1. Jangaroo 4.1 contains some updates that may be relevant for updating custom code:
New MXML compiler output: nested objects that resemble the MXML tree structure, rather than the old "sequential" code. The behavior at runtime is equivalent.
Stricter checks: Some additional syntactical and type errors are now detected. The compiler now finds illegal characters like additional
'<'in MXML code and performs more type checks that can reveal existing type errors. Even the properties of object literals with a type cast are now checked for existence and type-checked.Dependency checks: Like in Java, Jangaroo now also detects used, but undeclared Maven compile dependencies. This happens when code uses API from a module that is only available as a transitive dependency. Such missing dependencies must now be added, or the dependency check must be skipped.
As Jangaroo 4.1 prepares the studio-client workspace for a migration to TypeScript coming with CMCC11 we now require setting a "extNamespace" configuration for every Maven module build with the "jangaroo-maven-plugin". This has already been added for all blueprint modules. If you have own Maven modules using the "jangaroo-maven-plugin" we suggest setting the configuration to a common ActionScript package name that all ActionScript/MXML files below (src/main/joo and src/main/test) share. If there is no common package name just use "." (without quotes). If you just want to ignore this configuration for now you can set the flag "extNamespaceRequired" in the
blueprint-parent
pom.xml to
false
.
(CMS-19706)