Kevin,
this
is a bad joke, right? First we were asked to remove the
pointers to the JCP from the boilerplate specs, and now you
want us to re-add that same pointers to the web page? I
cannot find other words for this complete process other than
"chaotic mess". No users will ever understand that it makes
ANY sense to certify compliance against empty PDFs and at
the same time ask them to follow the rules laid out by the
JCP docs found ONLY on our web page. This might be legally
clear, but it is just ridiculous and awkward for most of us
normal people. A product which consists of empty PDFs does
not look like "finished", it looks like "not even started".
You might do that for a reason, but that reasons mit be the
wrong ones. You try to push out Jakarta EE just for the sake
of having a prominent brand, instead of providing a real
value to the end user. Waiting until the spec docs where
really legally safe or re-written would be the only thing
that proofs the power of our community, not showing
everybody that we actually couldn't. If the only problem was
"consistency", then the template should simply have ADDED a
link to JCP in ALL projects not having it already, instead
of removing it from the ones that had it. Also, Jakarta EE
is mostly an umbrella around otherwise independent APIs,
please don't forget that. There are lots of people just
interested in SOME specs, and they don't understand the
whole fuzz around this umbrella. ;-(
-Markus
Markus,
Until
the rest of the Specifications are contributed to Eclipse
(soon, I hear...), why not just update your "front page"
(wiki, gh pages, README, whatever) to point at the JCP page
for background information? This could be a temporary stop
gap until the Spec source is made available to you.
Also,
Bill's comments (and everybody else on the Spec Committee)
on the content of the skeletal specifications was to ensure
consistency. If we provided a common template with common,
consistent content (project name, scope statement,
copyright, license, etc), then Jakarta EE will look and feel
like a finished product. If we let every component do their
own thing, then it would just look like a hodge-podge of
information and would not provide the professional view that
we have. You may not agree, and that's fine. But, we were
doing this for a reason. Thanks.
---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Jakarta 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:
"Markus
KARG" <markus@xxxxxxxxxxxxxxx>
To:
"'Jakarta
EE community discussions'"
<jakarta.ee-community@xxxxxxxxxxx>
Date:
09/12/2019
06:20 AM
Subject:
[EXTERNAL]
Re: [jakarta.ee-community] Jakarta EE 8 Specs in PDF
Sent
by: jakarta.ee-community-bounces@xxxxxxxxxxx
I
know that. The question is, how shall the reader of the
Jakarte EE 8 spec know?
Von:Bill
Shannon [mailto:bill.shannon@xxxxxxxxxx]
Gesendet: Mittwoch, 11. September 2019 23:08
An: Jakarta EE community discussions; Markus KARG
Betreff: Re: [jakarta.ee-community] Jakarta EE 8 Specs
in PDF
As
Werner said, all the specs are on the JCP web site. You can
find a list of all the specs and links to the JSRs on the Java EE Platform web siteor Oracle's Java EE web site.
Markus KARG wrote on
9/11/19 11:06 AM:
Actually
it is hard for Jakarte EE 8 spec readers to find the Java EE
8 specs. The reason is that Bill Shannon (IIRC) enforced
that existing references form the boilerplate specs to the
Java EE specs have to get removed -- so we removed them, at
least for JAX-RS. It is rather funny that now you say,
people shall read exactly those specs… How shall they locate
them?
-Markus
Von:jakarta.ee-community-bounces@xxxxxxxxxxx[mailto:jakarta.ee-community-bounces@xxxxxxxxxxx]
Im Auftrag von Kevin Sutter
Gesendet: Mittwoch, 11. September 2019 10:59
An: Jakarta EE community discussions
Betreff: Re: [jakarta.ee-community] Jakarta EE 8 Specs
in PDF
Arjan
is correct. We have complete Specifications for the
Platform, Web Profile, CDI, and Bean Validation. The rest
of the Components have these skeletal specifications and
rely on the Javadoc for Jakarta EE 8. These other
Specifications will be filed as they complete their
copyright and IP clearances. We decided it was best to go
this route instead of waiting for all of the Component specs
to clear. Appreciate your patience.
I covered some of these process-related items in my "Jakarta
for dummEEs" talk yesterday at the JakartaOne Livestream
conference. Replays are available:
https://www.crowdcast.io/e/nztuljys/1
---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Jakarta 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: arjan
tijms <arjan.tijms@xxxxxxxxx>
To: Jakarta
EE community discussions <jakarta.ee-community@xxxxxxxxxxx>
Date: 09/11/2019
09:34 AM
Subject: [EXTERNAL] Re:
[jakarta.ee-community] Jakarta EE 8 Specs in PDF
Sent by: jakarta.ee-community-bounces@xxxxxxxxxxx
Hi,
It's "correct" in the sense that the real spec documents
haven't been transferred yet. The current ones that are
released (most of them) are just the bare minimum. We call
them boilerplate specs.
We expect that sometime in the future the existing Java EE
spec documents or a subset of those will be transferred.
Kind regards,
Arjan
On Wed, Sep 11, 2019 at 4:30 PM Gregor Kovač <kovica@xxxxxxxxx>
wrote:
Hi!
Specs are available at https://jakarta.ee/specifications/
"Jakarta EE Platform 8" has 242 pages, but "Jakarta Enterprise
Beans 3.2" has only 5 pages. Am I missing something? Looking
in a wrong place, ... ?
Best regards,
Kovi
_______________________________________________
jakarta.ee-community mailing list
jakarta.ee-community@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakarta.ee-community_______________________________________________
jakarta.ee-community mailing list
jakarta.ee-community@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakarta.ee-community
_______________________________________________
jakarta.ee-community
mailing list
jakarta.ee-community@xxxxxxxxxxx
To
change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakarta.ee-community
_______________________________________________
jakarta.ee-community mailing list
jakarta.ee-community@xxxxxxxxxxx
To change your delivery options, retrieve your password,
or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakarta.ee-community
