[ 
https://issues.apache.org/jira/browse/HADOOP-19861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18072918#comment-18072918
 ] 

ASF GitHub Bot commented on HADOOP-19861:
-----------------------------------------

Copilot commented on code in PR #8421:
URL: https://github.com/apache/hadoop/pull/8421#discussion_r3069014624


##########
hadoop-cloud-storage-project/hadoop-cos/pom.xml:
##########
@@ -113,6 +113,11 @@
       <scope>compile</scope>
     </dependency>
 
+    <dependency>
+      <groupId>jakarta.annotation</groupId>
+      <artifactId>jakarta.annotation-api</artifactId>
+    </dependency>
+

Review Comment:
   This PR introduces a new third-party dependency 
(jakarta.annotation:jakarta.annotation-api). It is not currently listed in 
LICENSE-binary, and there is no corresponding license text under 
licenses-binary/, so the binary licensing metadata will likely be out of date 
once this jar is bundled. Please add the dependency to LICENSE-binary under the 
appropriate license section and include the matching license file in 
licenses-binary/ (and NOTICE-binary if required by the dependency’s notice 
terms).





> 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]

Reply via email to