I'm not thrilled with the release cadence
table... The CDI example (and I know it's only an example) doesn't
represent reality. CDI 3.0 will not be part of Jakarta EE 8, it will
be CDI 2.0 (same as Java EE 8). And, the bump on the major version
for CDI just because it's part of Jakarta EE 9 doesn't represent proper
semantic versioning. It's an artificial bump, which is fine for the
platform spec. But, we should promote the use of proper semantic
versioning for the component specs. I've posted this comment to the
document as well... Maybe we should just replace CDI with "Comp"
or something generic? That would help a little bit…
I agree. It’s better not mentioning any particular components in the doc. Changing CDI to Comp is a good idea. Are we good with Kube and Istio references?
Or, are we going to change these to containerization and service
mesh?
I am voting for containerization and service mesh. And, are we going to expand on the innovation
issue that Bill highlighted? Or, were you waiting for me? :-)
Exactly. :)
Since I was conversing with Bill on the topic? Or, are we good
with the current content?
— Dmitry
--------------------------------------------------- Kevin Sutter STSM, MicroProfile and Java EE architect e-mail: sutter@xxxxxxxxxx Twitter: @kwsutter phone: tl-553-3620 (office), 507-253-3620 (office) LinkedIn: https://www.linkedin.com/in/kevinwsutterFrom:
Ivar Grimstad <ivar.grimstad@xxxxxxxxx>To:
EE4J PMC Discussions
<ee4j-pmc@xxxxxxxxxxx>Date:
06/07/2018 05:32 AMSubject:
Re: [ee4j-pmc]
Jakarta EE / EE4J Future Technical DirectionSent by:
ee4j-pmc-bounces@xxxxxxxxxxx Yes, it looks great!So, the next step would be to publish the document on
our web page.How about renaming the PMC News section to PMC Statements
and put it there (i.e. https://www.eclipse.org/ee4j/news/)IvarOn Thu, Jun 7, 2018 at 12:18 PM Dmitry Kornilov <dmitry.kornilov@xxxxxxxxxx>
wrote:Thanks, Martijn! Good job!— DmitryOn 6 Jun 2018, at 17:38, Martijn Verburg <martijnverburg@xxxxxxxxx>
wrote:Hi all,I've completed my sweep - you can check the changes through
the revision history - just yell at me if anything needs fixing :-)Cheers, MartijnOn 6 June 2018 at 15:59, Dmitry Kornilov <dmitry.kornilov@xxxxxxxxxx>
wrote:Martijn, I granted you edit rights to the document. Please
use it for grammar fixes only as we agreed.— DmitryOn 6 Jun 2018, at 16:17, Kevin Sutter <sutter@xxxxxxxxxx>
wrote:+1
--------------------------------------------------- Kevin Sutter STSM, MicroProfile and Java EE architect e-mail:
sutter@xxxxxxxxxx
Twitter: @kwsutter phone: tl-553-3620 (office), 507-253-3620(office) LinkedIn: https://www.linkedin.com/in/kevinwsutter
From: Richard
Monson-Haefel <rmonson@xxxxxxxxxxxxx> To: EE4J
PMC Discussions <ee4j-pmc@xxxxxxxxxxx> Date: 06/06/2018
09:12 AM Subject: Re:
[ee4j-pmc] Jakarta EE / EE4J Future Technical Direction Sent by: ee4j-pmc-bounces@xxxxxxxxxxx
+1
On Wed, Jun 6, 2018 at 7:39 AM, Ivar Grimstad <ivar.grimstad@xxxxxxxxx>
wrote: +1
On Wed, 6 Jun 2018, 14:38 Dmitry Kornilov, <dmitry.kornilov@xxxxxxxxxx>
wrote: I am fine to give Martijn access to contribute grammar fixes. What others
think?
— Dmitry
On 6 Jun 2018, at 10:47, Martijn Verburg <martijnverburg@xxxxxxxxx>
wrote:
Hi all,
Apologies for not commenting on the doc earlier! Some quick thoughts
(my own, other LJC members have commented individually):
Overall:
Is it possible to get suggestions mode switched back on? I'd just
like to suggest a bunch of grammatical changes, I suspect the merge of
various suggestions have created a few bits of awkward phrasing.
I'd also like to add some structure to it in the form of headings and a
TOC.
Open for Innovation
I like this and combined with a robust deprecation capability means that
if a latest and greatest innovation ends up being short lived then it can
be gracefully retired.
Splitting the TCK
I like this as well but would also like to see a statement that an objective
should be to make the running onf a TCK and checking results consistent.
That is, I would like to be able to go to any sub project and run something
like mvn clean test -Ptckand view an XML/HTML report at the end (or whatever format is deemed useful.
JPMS
I've started a new initiative with the Maven folks and Ray Tsang from Google
to start data mining Maven central and see how the ecosystem is embracing
JPMS. I think adding the automatic module name is a no brainer but
care will need to be taken that when embracing the module system that the
resulting implementations / specs can be used both on the module path and
classpath. This is easier said than done.
There's a few Maven plugins AdoptOpenJDK have been working on (jdeps,
jdeprscan, jsplitpkgcan) to help alleviate this.
I'm looking for more volunteers for these various projects!
Maven
I'm OK with this, yes some folks will argue that Gradle is technically
superior, but Maven encourages a std "I don't have to think"
behaviour.
Deprecation, Soft Dependencies, CDI and Config
loose coupling and graceful deprecation are good things :-). CDI
and Config seem sensible mechanisms to achieve that.
Release Cadence
The wording here is quite confusing, I think a reworking of this with a
sample table outlying how this would work will be helpful (I'm happy to
do this).
Cheers, Martijn _______________________________________________ ee4j-pmc mailing list ee4j-pmc@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe
from this list, visit https://dev.eclipse.org/mailman/listinfo/ee4j-pmc
_______________________________________________ ee4j-pmc mailing list ee4j-pmc@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe
from this list, visit https://dev.eclipse.org/mailman/listinfo/ee4j-pmc -- Java Champion, JCP EC/EG Member, EE4J PMC,
JUG Leader _______________________________________________ ee4j-pmc mailing list ee4j-pmc@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe
from this list, visit https://dev.eclipse.org/mailman/listinfo/ee4j-pmc
_______________________________________________ ee4j-pmc mailing list ee4j-pmc@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe
from this list, visit https://dev.eclipse.org/mailman/listinfo/ee4j-pmc
_______________________________________________ ee4j-pmc mailing list ee4j-pmc@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe
from this list, visit https://dev.eclipse.org/mailman/listinfo/ee4j-pmc
_______________________________________________ ee4j-pmc mailing list ee4j-pmc@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe
from this list, visit https://dev.eclipse.org/mailman/listinfo/ee4j-pmc
_______________________________________________ ee4j-pmc mailing list ee4j-pmc@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe
from this list, visit https://dev.eclipse.org/mailman/listinfo/ee4j-pmc
_______________________________________________ ee4j-pmc mailing list ee4j-pmc@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe
from this list, visit https://dev.eclipse.org/mailman/listinfo/ee4j-pmc --
Java Champion, JCP EC/EG Member, EE4J PMC, JUG Leader_______________________________________________ ee4j-pmc mailing list ee4j-pmc@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe
from this list, visit https://dev.eclipse.org/mailman/listinfo/ee4j-pmc
_______________________________________________ ee4j-pmc mailing list ee4j-pmc@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/ee4j-pmc
|