New Java Deployment Style

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:

  1. 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).
  2. 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.
  3. Non-core components should be able to plugged into multiple versions of JRE, like JSSE, JGSS,...

 

Comments:

Post a Comment:
  • HTML Syntax: NOT allowed
About

This blog has a comments managing system that requires me to approve each comment manually. Please do not re-post and I will reply it (if I have an answer) when I get pinged.

Search

Top Tags
Categories
Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today