[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [jakartaee-platform-dev] NEW VOTE 2: Leave Jakarta Activation in javax namespace
|
Just to clarify your
statements...jakarta.activation
would be required due to javamail, ejb, and jax-rs dependenciesbut, jakarta.xml.bind,
jakarta.xml.ws, jakarta.xml.soap, and jakarta.jws would all be optional.Accurate? I'd
be okay with that. I just don't see how jakarta.activation could
be optional.
---------------------------------------------------
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/kevinwsutterFrom:
"Steve
Millidge (Payara)" <steve.millidge@xxxxxxxxxxx>To:
jakartaee-platform
developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>Date:
12/05/2019
09:07Subject:
[EXTERNAL]
Re: [jakartaee-platform-dev] NEW VOTE 2: Leave Jakarta
Activation in
javax namespaceSent
by: jakartaee-platform-dev-bounces@xxxxxxxxxxx
By
also moving all the JAX-WS etc. to Jakarta namespace and making them optional?
From:jakartaee-platform-dev-bounces@xxxxxxxxxxx <jakartaee-platform-dev-bounces@xxxxxxxxxxx>
On Behalf Of Kevin Sutter
Sent: 05 December 2019 14:22
To: jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Subject: Re: [jakartaee-platform-dev] NEW VOTE 2: Leave Jakarta Activation
in javax namespace
Steve,
How do we make jakarta.activation optional if so many packages have dependencies
on it? If we can do that, I'm in favor of that approach. I
just don't see how that works with Activation.
---------------------------------------------------
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: "Steve
Millidge (Payara)" <steve.millidge@xxxxxxxxxxx>
To: jakartaee-platform
developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Date: 12/05/2019
04:02
Subject: [EXTERNAL]
Re: [jakartaee-platform-dev] NEW VOTE 2: Leave Jakarta Activation
in javax namespace
Sent by: jakartaee-platform-dev-bounces@xxxxxxxxxxx
0
My position is shifting towards move all these to Jakarta but make optional
and make Java SE 11 the base as that may be the consistent option with
greater consensus.
From:jakartaee-platform-dev-bounces@xxxxxxxxxxx
<jakartaee-platform-dev-bounces@xxxxxxxxxxx>
On Behalf Of Kevin Sutter
Sent: 04 December 2019 23:33
To: jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Subject: [jakartaee-platform-dev] NEW VOTE 2: Leave Jakarta Activation
in javax namespace
Preamble:
https://www.eclipse.org/lists/jakartaee-platform-dev/msg01180.html
Please vote +1/0/-1 on the following. Any non +1 vote, please provide
reasoning in your reply. Thank you!
Required (leave in javax namespace) - Vote
• Jakarta Activation 1.2
Jakarta Activation was one of the APIs dropped from Java SE 11 per JEP
320. Several Jakarta EE technologies require the use of Jakarta Activation,
so we can't make it optional. It is required for Jakarta EE. This
vote is for whether we move this feature to the jakarta namespace (-1)
or leave it in the javax namespace (+1). The recommendation is to
Jakarta Activation in the javax namespace. And, if at some later
date, this API needs to evolve and move to the jakarta namespace, then
we can deal with the ripple effect on other specs at that time.
Note: A -1 vote indicates that you want Jakarta Activation to
be migrated to the jakarta namespace. And, if we do that, then there
is a ripple effect that will also require corresponding changes to jaxb,
jax-ws, and soap. Thus, a -1 vote here means that Vote 3 on the other
Optional specs won't apply. That is, voting -1 here and +1 on Vote
3 doesn't make any sense. Check out this tool from Tomitribe: https://www.tomitribe.com/jakarta/ns/poll/vote
Note2: This assumes that all of the existing Specification PRs
for these technologies are properly brought under the EE4J umbrella. We
discussed these at the Spec Committee call today and we are well aware
that we need to move on these and get them approved.
• https://github.com/jakartaee/specifications/pulls?q=is%3Apr+is%3Aopen+label%3Ajavase
---------------------------------------------------
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