|
Minutes from Jakarta EE Steering Committee Meeting August 21
Attendees:
Fujitsu: Kenji Kazumura, Mike Denicola
IBM: Dan Bandera
Oracle: Will Lyons
Payara: Steve Millidge
Red Hat: Mark Little
Tomitribe: David Blevins, Richard Monson-Hafael
Martijn Verburg
Ivar Grimstad
Eclipse: Mike Milinkovich
Review of Minutes from Prior Meeting
The minutes of July 31 Steering Committee meeting and
August 2 budget meeting were approved.
Minutes of August 7 meeting will be reviewed next
meeting.
Updates on Oracle contribution
We have made significant progress. Since the
Steering Committee last met Oracle has internally approved 34
repositories for contribution to Eclipse; we are in the process
of making these contributions now.
After these contributions are completed, the following are the
remaining contributions:
- Five more repositories with GlassFish RI related code
requiring internal Oracle approval.
- Repositories containing Maven tools and scripts
- Doc/web-site/other non-GF code (not required to complete
Java EE certification)
- TCKs
We are actively engaged in completing the TCK license
agreement, after which we will move forward on TCK
contributions.
We are nearly ready to begin the Eclipse GlassFish build
process. We will gradually update Maven build coordinates from
current Oracle references to EE4J.
To summarize, we have made significant progress recently with
Oracle approvals, and this will be manifested soon in many new
contributions. We are approaching the point where Eclipse
GlassFish builds can begin.
Budget Meeting Tomorrow
Reviewed plan for budget meeting tomorrow. Oracle
noted it is prepared to make a 3 year funding commitment.
Code One/ECE Messages
At the last meeting it was suggested Oracle propose
Jakarta EE messaging. The following draft messages were
proposed for discussion.
Announcing Eclipse GlassFish.
GlassFish contributions to Jakarta EE are complete
and Eclipse GlassFish is certified as Java EE 8 compatible
[adjust statement based on actual level of completion]. We
expect Eclipse GlassFish sources will become the basis for
implementations of Jakarta EE specifications.
Java EE TCKs are open sourced.
The Java EE 8 Technology Compatibility Kits have
been contributed and are available in Open Source. We expect
these to be the basis for Jakarta EE 8 compatibility tests for
branding of multiple independent implementations of Jakarta EE
specifications.
We [Oracle and other WG members] are committed to Jakarta
EE.
We [Oracle and other WG members] remain committed to
enabling evolution of the Java EE 8 technologies, including
evolution of the javax namespace, in Jakarta EE specifications
for cloud native Java. [Hope to identify specific
milestone]. We [Oracle and other WG members] have committed
to funding this effort at the Eclipse foundation.
We [Oracle and other WG members] will leverage Jakarta EE.
We [Oracle and other WG members] intend to leverage
Jakarta EE technologies and cloud native Java in its product
and service offerings. [Each WG member may have its own
announcement that will...] leverage Jakarta EE and/or Eclipse
GlassFish technology, and/or will support Java EE 8, Jakarta
EE 8 and evolution of Jakarta EE.
With respect to the final two items listed above, Mark Little
stated that he felt these statements were reiterating statements
that have already been made some time ago, and that he would
like that either:
- We announce at Code One / ECE that an agreement is in
place between Oracle and Eclipse, that enables evolution of
the Java EE technologies, including use of the javax
namespace for evolution of these technologies, or
- That we announce a commitment to come to such an agreement
by the end of the calendar year.
This would demonstrate progress towards spec process
definition. Both Oracle and Eclipse stated they did not
believe the first item above was achievable, based on progress
achieved on legal agreements to date.
Given that, statement Mark offered, as had been offered by IBM
in the prior meeting, that Red Hat and IBM would be willing to
engage with Oracle management at an executive level to push for
such commitment. Mark said he believes we would need to
re-evaluate the initiative if we could not make progress towards
that year end goal.
It was pointed out that significant progress can be made on the
specification process independent of the legal issues discussed
above. The example of JNoSQL was cited, where there is no
dependency on the legal issues described above.
Will Lyons will consider the Red Hat/IBM offer of escalation and
Mike Milinkovich will include discussion of how to make progress
on the specification process at the next Spec Committee meeting.
Spec Committee Update
See comments on Spec Committee actions above.
Marketing Committee Update
August - December Marketing plan distributed by
Thabang Mashologu on August 18.
Oracle is eager to participate in EclipseCon Europe. Following
up between Eclipse and Oracle.
PMC Update
No significant update for this group.
Recruitment of new members; Elections
Note discussed.
Open issue - will there be an additional PMC representative on
the Steering Committee.
Planned Jakarta EE certifications
Not discussed
What other app servers, besides GlassFish can we expect on
Jakarta EE 8 - get input from Steering Committee.
Wildfly - name clarification needed from RedHat ?
IBM Liberty
Fujitsu
Payara - ?
Weblogic - ?
TomiTribe - ?
Legal Documents
Making progress on TCK license agreeement per above.
|
