Upgrade required to get fix for bug 1155823.  The fix has been committed for the as yet unreleased 1.3.5 and 1.4.0 versions.

Currently the master branch (what will be 1.4.0) also has the following changes compared to the 1.3 branch:
 MODULES-183 Child-first loading 5191f7de2b522ed96866e7acd58776638011942a
 OS/400 support 90d68d4f7e21f5df674057e2ef8c5af04d1fa0ad
 cli-help-fix e5798f726ac92797f106efcec44087912e4b0309
 [MODULES-185] More robust native library detection 57d64097972c61d3ae8d20caaf82b5146f652607
 Detect iWMMX2, verify that it is backwards compat e228402be4977649f923212975f58103b38e64a3
 Disable parallel check for 1.3.x, leave enabled for 1.4.x and higher cf37567cd8c5da814cae78a430e0e9c752d2733b
 Support for application preferences factory d0fce50c7b2cb52edffccbdbeda71239c820b886
 Slightly improved error reporting in some cases 453d89c8a9ddb226c9223f19274df71f3affbad6
 [MODULES-189] Enforce a minimum JVM spec version f7e2861ecbb459f6ded44f3173ea4c4d902c90b2   (1.6+, so okay)
 Relax module name restrictions 8dfb91d5345eb0623c91ed425c5260072820928d
 Move to ASL 2.0 licensing model 56458db45d5a42755220b8b43c5b424c86c2f5c5
 Remove an awful lot of CRs 2b4e683e8927a0276f21ff225f596787c3e46771


I asked dmlloyd and he did not mind either way for upgrading to 1.3.5 versus 1.4.0. The only potentially problematic change I can see is MODULES-183, but if anything is relying on the current behaviour it is arguably broken already.


If 1.4.0 is considered to risky, then we should instead upgrade to 1.3.5 (once released).