[
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
|
-1 as well.
Reason: javax.activation is relatively small and separated. And it barely touches other APIs.
BUT: it is used in many applications. E.g. the DataHandler and DataContentHandler.
Thus for making the big-bang migration as easy as possible we should go and migrate it over as well.
LieGrue,
strub
> Am 05.12.2019 um 00:32 schrieb Kevin Sutter <sutter@xxxxxxxxxx>:
>
> 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
