[
https://issues.apache.org/jira/browse/HADOOP-19861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18076152#comment-18076152
]
ASF GitHub Bot commented on HADOOP-19861:
-----------------------------------------
slfan1989 commented on PR #8421:
URL: https://github.com/apache/hadoop/pull/8421#issuecomment-4318223536
@pan3793 I understand the suggestion to use `JSpecify`, and the direction
makes sense. For `HADOOP‑19861`, the current scope is limited to the
`javax→jakarta` migration in `hadoop‑cos`, so I prefer to keep the change
minimal and low‑risk. Adopting `JSpecify` involves a broader decision on
nullness annotations, dependency management, and tooling support, which should
be discussed and driven as a separate proposal. I suggest we keep this change
as a `jakarta` migration, and if needed I can open a separate `JIRA` or draft
to plan `JSpecify` adoption. Does that sound reasonable?
cc: @steveloughran
> Migrate hadoop-cos from javax.annotation to jakarta
> ---------------------------------------------------
>
> Key: HADOOP-19861
> URL: https://issues.apache.org/jira/browse/HADOOP-19861
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: hadoop-cos
> Affects Versions: 3.5.1, 3.6.0
> Reporter: Shilun Fan
> Assignee: Shilun Fan
> Priority: Major
> Labels: pull-request-available
>
> The hadoop-cos module currently uses javax.annotation.Nullable from the
> legacy javax.annotation-api package. As part of the Jakarta EE transition, we
> should migrate to jakarta.annotation.Nullable.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
