87:
22:
114:
The EC is responsible for approving the passage of specifications through key points of the JCP and for reconciling discrepancies between specifications and their associated test suites. There were originally two ECs: the SE/EE EC oversees the Java technologies for the desktop/server space (with
130:
The two ECs were merged in August 2012, with the passage of JSR 355. The current membership consists of large Java vendors, such as Oracle, IBM, HP, Fujitsu & Red Hat. Also represented are "end-user" companies, including
Goldman Sachs, Credit Suisse & TOTVS. Two Java User Groups,
110:(JCP). The EC represents both major stakeholders and a representative cross-section of the Java Community. It is composed of 16 JCP members plus a non-voting chair. The chair of the EC is a member of the Process Management Office (PMO). The 16 voting members are selected from JCP members.
51:
123:
specifications) and the ME EC oversees the Java technologies for the consumer/embedded space (with responsibility for the
73:
44:
86:
163:
149:
34:
159:
38:
30:
210:
107:
55:
8:
172:
Review maintenance revisions and possibly require some to be carried out in a new JSR.
90:
The JCP Executive
Committee meeting of January 2001, as held in Bedford, Massachusetts
188:
135:
and the London Java
Community also hold seats, as does the Eclipse Foundation.
204:
103:
194:
158:
Give final approval to completed specifications and their associated
132:
124:
120:
116:
197:, Appendix A: Executive Committee Policies and Procedures.
175:
Approve transfer of maintenance duties between members.
191:
information at the Java
Community Process web site.
102:) is the group of members guiding the evolution of
169:Decide appeals of first-level TCK test challenges.
202:
43:but its sources remain unclear because it lacks
155:Approve draft specifications for public review.
144:Each Executive Committee is expected to:
74:Learn how and when to remove this message
85:
203:
152:(JSR) for development within the JCP.
15:
139:
13:
14:
222:
20:
1:
182:
164:Technology Compatibility Kits
178:Provide guidance to the PMO.
7:
150:Java Specification Requests
10:
227:
160:Reference Implementations
29:This article includes a
189:JCP Executive Committee
115:responsibility for the
96:JCP Executive Committee
58:more precise citations.
195:JCP 2 Process Document
108:Java Community Process
91:
89:
106:technology in the
92:
31:list of references
84:
83:
76:
218:
140:Responsibilities
127:specification).
79:
72:
68:
65:
59:
54:this article by
45:inline citations
24:
23:
16:
226:
225:
221:
220:
219:
217:
216:
215:
201:
200:
185:
142:
136:
111:
80:
69:
63:
60:
49:
35:related reading
25:
21:
12:
11:
5:
224:
214:
213:
199:
198:
192:
184:
181:
180:
179:
176:
173:
170:
167:
156:
153:
141:
138:
82:
81:
39:external links
28:
26:
19:
9:
6:
4:
3:
2:
223:
212:
211:Java platform
209:
208:
206:
196:
193:
190:
187:
186:
177:
174:
171:
168:
165:
161:
157:
154:
151:
147:
146:
145:
137:
134:
128:
126:
122:
118:
112:
109:
105:
101:
97:
88:
78:
75:
67:
57:
53:
47:
46:
40:
36:
32:
27:
18:
17:
143:
129:
113:
99:
95:
93:
70:
61:
50:Please help
42:
56:introducing
183:References
64:April 2014
162:(RI) and
205:Category
148:Select
133:SouJava
125:Java ME
121:Java EE
117:Java SE
52:improve
166:(TCK).
37:, or
119:and
104:Java
94:The
207::
100:EC
41:,
33:,
98:(
77:)
71:(
66:)
62:(
48:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
