Moving Development Environment for Web to own project
Updating the sample to benefit from model and MVVC bindings
Keeping just the part of the server that is needed for the dew system
Adding license to the nbactions.xml file
We don't need the harness in dew at all
Configuring the exec:exec inside pom.xml, so it can be used from command line
Allow class name change in the java code by referencing the it via ${fqn} from HTML
Keep the VM code, don't regenerate it every time
Prevent against NPE
Allows two isolated bck2brwsr VM in a single JavaScript page/context
[maven-release-plugin] prepare release bck2brwsr-0.3
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release release-${releaseVersion}
[maven-release-plugin] prepare for next development iteration
Don't deploy dew
[maven-release-plugin] prepare release release-0.5
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release release-0.6
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release release-0.7