New Java Deployment Style
By Weijun-Oracle on Mar 01, 2007
There're quite a lot of new proposals for the deployment style of next-version JRE, some focused on the end-user experience, some on updating schedule, some on component dividing, some on enterprise deployment. As a JRE user, I agree on all aspects, and as an developer, I hope they are carried out in a consistent way around a solid architecture and a clean design, so that a few core concepts can offer multiple purposes in a nice style.
For me, I especially would like these points becoming true:
- Any code change should be labeled enhancement, normal bug fix, or security bug fix. The last one should be released as hot patch (detailed descriptions for licensees).
- JRE should be divided into components in a reasonable granularity (small, but no smaller. Developers should be satisfied by re-organizing them in most cases, instead of hacking inside and create special releases, aka, forking). The components have dependencies among them, there are versions. Sometimes two components may be parallel (alternative), which means one and only one can be activated.
- Non-core components should be able to plugged into multiple versions of JRE, like JSSE, JGSS,...