BladeRunnerJS v0.4
Pre-release
Pre-release
BladeRunnerJS v0.4
Our first major milestone containing a number of bug fixes, improvements and new features.
Release highlights include:
- NodeJS style App source code support
- Improved BRJS model and plugin interfaces
- The BRJS model now uses the Java7 File Watcher Service to enable caching and minimise the amount of dependency analysis that has to be executed
- The
CompositeBundler
plugin now allows both NamespacedJS and NodeJS style source code to be used in the same App CSSBundler
plugin uses the new BRJS modelXMLBundler
andHTMLBundler
changed to use the new model and plugin interfaces- Basic support for NodeJS libraries
- Integrated JSTestDriver to use the new BRJS model to generate test bundles
- A number of other bug fixes and minor improvements
Known Issues
- Due to some EcmaScript5 uses BRJS does not currently support IE8
- Workaround: There is no workaround but this is something we will fix in the near future
- CPU usage issues when BRJS server is left running for a prolonged period of time
- Workaround: Restart the BRJS server once every 30-60 minutes
- The
CSSResource
plugin is not fully implemented. As a result images are not available in workbenches and exports WARs.- Workaround: Images can be referenced using an absolute URL to load them directly from disk rather than via the BRJS 'bundling' mechanism
- Due to the latency of the File Watch Service on OSX it can sometimes take several seconds for changes to files to be picked up when a page is refreshed
- Workaround: Either wait a few seconds and refresh the page again, or if you're in a hurry just restart the BRJS server
- Due to a bug in Java, the JVM can occasionally crash on Windows when BRJS attempts to close File Watchers.
- Workaround: Unfortunately there is no workaround. Oracle are aware of the issue and we will also be making changes to aleviate the issue in a future release
Closed Issues
54 issues closed; 32 labelled bug, feature, enhancement or experience from 6 milestones: https://github.com/BladeRunnerJS/brjs/issues?milestone=4; https://github.com/BladeRunnerJS/brjs/issues?milestone=5; https://github.com/BladeRunnerJS/brjs/issues?milestone=8; https://github.com/BladeRunnerJS/brjs/issues?milestone=9; https://github.com/BladeRunnerJS/brjs/issues?milestone=10; https://github.com/BladeRunnerJS/brjs/issues?milestone=11
- add tag handler support #261
- add aliasing support to the new bundlers #259
- make the NamespacedJS bundler plugin append package definitions to the top of the bundle #257
- convert JS bundler to a bundler plugin so it uses the new model #231
- add NodeJS style class support to new bundling infrastructure #230
- add NamespacedJS style class support to new bundling infrastructure #229
- Improve developer debug experience by allowing individual JS files to be served in an app #46
- Node.js module-style code support #11
- finalise the bundler interface design #278
- come up with a good design for managing different types of JsLibs #277
- Workbenches show 500 error #305
- ConcurrentModificationException is thrown when BRJS attempts to serve multiple requests #300
- upgrade knockout #294
- upgrade jQuery #293
- create a default EventHub #204
- allow new style js code to be used in tests #322
- Using require('fell') pulls in unnecessary additional dependencies #308
- Bundler Script transferred as plain/text should be application/x-javascript (or similar) #307
- improve performance in BRJS core and the model #276
- make thirdparty bundler part of the new infrastructure #238
- update templates so example JS file uses new JS style #20
- Add support for js-patches #335
- UTF8 bundling tests fail when run via cmd line #334
- convert i18n bundler to use the new bundler plugin infrastructure #237
- convert image bundler to use the new bundler plugin infrastructure #236
- convert HTML bundler to use the new bundler plugin infrastructure #235
- convert XML bundler to use the new bundler plugin infrastructure #234
- convert CSS bundler to use the new bundler plugin infrastructure #233
- Websphere throw exception when file not found. Should only return 404 error #225
- Filter fixes for websphere #224
- investigate and fix workbench issues we're currently seeing #349
- Deploy to Tomcat by dropping .WAR into webapps folder stops root app working #192
Parts of this release note have been auto-generated. If you notice any problems with it tell us