Do not change the schema location for Jakarta EE 8. It will need to
change for Jakarta EE 9 if/when the deployment descriptors are
changed.
Kevin Sutter wrote on 7/4/19 3:03 PM:
Thanks, Emily!
1. Java SE is fine to use.
2. Good question on schema location. For
now, I think the current location is fine.
-- Kevin
Can I clarify for the following:
1. I think Java SE is still allowed to be mentioned
in the spec. Please correct me if I am wrong.
2. For the schemas for Jakarta EE, where should
these be hosted?
e.g. for the following one:
I
guess it needs to be hosted by eclipse site. Please
clarify.
At
the moment, I just updated javaee to jakartaee,
which might not be complete.
Thanks
Emily
The direction from our trademark specialist is to
put the TM after Jakarta.
https://www.eclipse.org/legal/logo_guidelines.php
says Jakarta and Jakarta EE are asserted
https://www.eclipse.org/projects/tools/trademarks.php
says Jakarta EE is filed
so would be useful
to know where to put the tm in the spec
docs etc. until Jakarta EE is registered.
From: jakartaee-platform-dev-bounces@xxxxxxxxxxx
<jakartaee-platform-dev-bounces@xxxxxxxxxxx>
On Behalf Of Kevin Sutter
Sent: 04 July 2019 16:57
To: jakartaee-platform developer
discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Subject: Re:
[jakartaee-platform-dev] Platform and
WebProfile specs ready to be
"jakarta-ized"
Paul, according to our
trademark page, it says that "Jakarta EE"
is trademarked. It says nothing about
"Jakarta" itself being trademarked...
Which is correct?
Please keep the ™
after Jakarta.
Hi Kevin,
I would like
to assist on this. I am quite
naive on this and would like to
clarify something. There is the
use of Java™ Platform Enterprise
Edition. Should it be changed to
Jakarta™ Platform Enterprise
Edition or just Jakarta Platform
Enterprise Edition? Getting rid
of the TM or keeping it.
I made a
stab at updating the Security
section:
I
should point out that the
chapter files for the
Platform and WebProfile
are in the following
corresponding
directories...
https://github.com/eclipse-ee4j/jakartaee-platform/tree/master/specification/src/main/asciidoc/platform
https://github.com/eclipse-ee4j/jakartaee-platform/tree/master/specification/src/main/asciidoc/webprofile
No
other files need to be
modified for this
requested exercise.
You
can either do a "mvn clean
install" and look at the
generated pdf or html.
Or, you can view the
corresponding sections via
these urls:
https://github.com/eclipse-ee4j/jakartaee-platform/blob/master/specification/src/main/asciidoc/platform/Platform.adoc
https://github.com/eclipse-ee4j/jakartaee-platform/blob/master/specification/src/main/asciidoc/webprofile/WebProfile.adoc
Have fun!
---------------------------------------------------
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:
"Kevin
Sutter" <sutter@xxxxxxxxxx>
To:
"jakartaee-platform
developer discussions"
<jakartaee-platform-dev@xxxxxxxxxxx>
Date:
07/03/2019
10:19 PM
Subject:
[EXTERNAL]
[jakartaee-platform-dev]
Platform and WebProfile
specs ready to be
"jakarta-ized"
Sent
by: jakartaee-platform-dev-bounces@xxxxxxxxxxx
Hi,
Most of you know that the
Java EE Platform and
WebProfile specs have now
been contributed to
Eclipse and ready to go
through the transformation
to Jakarta Platform and
WebProfile specs:
https://github.com/eclipse-ee4j/jakartaee-platform/tree/master/specification
I have broken up the
individual specs into
slightly more manageable
pieces of asciidoc (each
spec used to be one giant
asciidoc file). I broke
them up by chapters. Of
course, some are larger
than others, but at least
we can now divide and
conquer the effort in
front of us. Many of you
have been asking "how can
I help?". Now's your
chance. If you are
interested and available,
we would appreciate PRs
with cleaning up the
various sections of these
two spec documents.
The cleanup required is
mostly tedious work.
-
The
main thing is changing
"Java EE" to "Jakarta
EE".
-
Modifying
references to the JCP
with corresponding
Eclipse processes.
-
References
to existing Java EE
technologies, acronyms,
and JSRs are okay as
long as they are
properly attributed.
-
Be
careful not to modify
the semantics or
behavior -- we need
Jakarta EE 8 to be
functionally equivalent
to Java EE 8.
We
are looking for the
minimal work required. At
this point, do not further
subdivide the asciidoc
files. I would suggest
keeping the PRs short and
simple. Don't try to do
"everything" in one PR.
You don't even have to
complete a whole chapter
in a single PR. Maybe
identify the subsections
covered in the title of
your PR. Shorter PRs will
be easier for the
committers to evaluate and
merge into master.
Reference the list of
existing PRs before
starting on a chapter to
avoid duplication of
effort.
I am sending out this
request now since many of
us in the US will be out
for the extended weekend.
There are a few committers
in other parts of the
world, so hopefully we'll
make some progress over
the weekend. I didn't
want to wait until Monday
to start this effort since
we need to have these spec
docs ready by July 15.
Thanks for your help!
---------------------------------------------------
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_______________________________________________
jakartaee-platform-dev
mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To change your
delivery options,
retrieve your password,
or unsubscribe from this
list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
_______________________________________________
jakartaee-platform-dev
mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery
options, retrieve your
password, or unsubscribe
from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
_______________________________________________
jakartaee-platform-dev mailing
list
jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options,
retrieve your password, or
unsubscribe from this list,
visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options,
retrieve your password, or
unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options,
retrieve your password, or unsubscribe
from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your
password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your
password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
--
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password,
or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
|
