BladeRunnerJS v0.4

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 model
• XMLBundler and HTMLBundler 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}

BladeRunnerJS v0.3

BladeRunnerJS v0.3

• Another bugfix and maintenance release before completing bundler plugins, content plugins and minifiers.
• Adds support for bundler plugins, albeit with limited functionality until the next release.
• CompositeJsBundlerPlugin supports minifier plugins so custom minifiers can be used.
• Added ContentPlugins, which uses a subset of BundlerPlugin functionality, to support use cases such as automatic app cache manifests.
• Improved visibility of errors when a user uses an incorrect command.

---

Closed Issues

^{17 issues closed; 6 labelled bug, feature, enhancement or experience - https://github.com//BladeRunnerJS/brjs/issues?milestone=3}

• Difficult to see error message when I use an incorrect command (#245)
• Provide a ContentPlugin interface so plugins can be written to support things like an appcache manifest (#241)
• Improved logging for new bundling infrastructure (#228)
• Complete new bundling infrastructure (#227)
• add minifier plugin support to new bundling infrastructure (#162)
• create a J2EE filter that allows the bundlers to be addressed with URLs that have the correct file extensions (#42)

_{Parts of this release note have been auto-generated. If you notice any problems with it, tell us}

BladeRunnerJS v0.2

BladeRunnerJS v0.2

• renamed brjs start command to serve
• brjs test-server command now accepts an optional --no-browser flag to start the test server without requiring browser config to be setup
• better error handling messages for when configuring test browsers
• general bug fixes

---

Closed Issues

^{19 issues closed; 8 labelled bug, feature or enhancement - https://github.com//BladeRunnerJS/brjs/issues?milestone=2}

• BRJS is unable to import an app due to reference to deleted jsdoc template folder (#219)
• create the infrastructure around bundlers to prove the architecture for Bundlers, BundlerSourceProvider etc (#197)
• test-runner.conf browsers should not be required if 'test-server -no-browser' is executed (#183)
• minor tweaks to the tutorial app in GitHub (#173)
• provide better feedback if an invalid browser is used for tests (#166)
• show the brjs help menu if I dont provide a command to run (#138)
• fix the js-test-driver json bug that often prevents you seeing your errors (#52)
• Alias brjs command "start" to "serve" (#9)

_{Parts of this release note have been auto-generated. If you notice any problems with it, tell us}

Initial release of BladeRunnerJS. Hurray!

BladeRunnerJS v0.1

• the initial release of BladeRunnerJS
• see http://bladerunnerjs.org/blog/bladerunnerjs-v0-1-released/ for the release announcement

---

Closed Issues

^{26 issues closed; 6 labelled bug, feature, enhancement or experience - https://github.com//BladeRunnerJS/brjs/issues?milestone=1}

• Stop logging to browser console during tests (#136)
• running all JS tests for the BRJS build sometimes hangs (#132)
• The dev filters are throwing java.lang.NullPointerException with appConf causing tomcat to not load apps (#129)
• populate brjs-core and create compatibility stubs (#61)
• populate brjs-ui and create compatibility stubs (#60)
• As a developer I expect plugins to have a .jar file extension (#22)

_{Parts of this release note have been auto-generated. If you notice any problems with it, tell us}