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

ASF GitHub Bot commented on NUTCH-3130:
---------------------------------------

lewismc commented on PR #869:
URL: https://github.com/apache/nutch/pull/869#issuecomment-3420401421

   I did want to also note, there are 15 instances of the @Deprecated 
annotation across 9 files in the codebase:
   src/java/org/apache/nutch/tools/CommonCrawlFormatFactory.java - 1 instance
   
src/plugin/lib-http/src/test/org/apache/nutch/protocol/http/api/TestRobotRulesParser.java
 - 2 instances
   src/test/org/apache/nutch/crawl/CrawlDbUpdateUtil.java - 3 instances
   src/test/org/apache/nutch/crawl/CrawlDBTestUtil.java - 3 instances
   src/java/org/apache/nutch/util/NutchJob.java - 1 instance
   src/java/org/apache/nutch/protocol/RobotRulesParser.java - 1 instance
   src/java/org/apache/nutch/protocol/ProtocolStatus.java - 2 instances
   src/java/org/apache/nutch/net/protocols/ProtocolException.java - 1 instance
   src/java/org/apache/nutch/crawl/Generator.java - 1 instance
   
   I'm not sure whether is the correct time to be removing these methods but if 
we decide to keep them we should definitely augment the Javadoc to detail the 
replacement API usage.




> Address deprecated API usage across Nutch codebase and build
> ------------------------------------------------------------
>
>                 Key: NUTCH-3130
>                 URL: https://issues.apache.org/jira/browse/NUTCH-3130
>             Project: Nutch
>          Issue Type: Improvement
>          Components: build, ci/cd, dependency
>    Affects Versions: 1.21
>            Reporter: Lewis John McGibbney
>            Assignee: Lewis John McGibbney
>            Priority: Major
>             Fix For: 1.22
>
>
> A long time ago I performed a similar task 
> (https://issues.apache.org/jira/browse/NUTCH-1273) to address all deprecation 
> warnings flagged across the Nutch codebase.
> This time around I want to do the same but also plan to include a deprecation 
> check as part of GitHub CI so we keep on top of deprecation issues into the 
> future.
> Patch coming up.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to