[ 
https://issues.apache.org/jira/browse/CSV-301?focusedWorklogId=800448&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-800448
 ]

ASF GitHub Bot logged work on CSV-301:
--------------------------------------

                Author: ASF GitHub Bot
            Created on: 13/Aug/22 23:19
            Start Date: 13/Aug/22 23:19
    Worklog Time Spent: 10m 
      Work Description: kinow commented on PR #250:
URL: https://github.com/apache/commons-csv/pull/250#issuecomment-1214245052

   Good point @garydgregory  , I just logged in to JIRA to check the CSV 
project releases, and looks like the 2.0 has no issues so far.
   
   
![image](https://user-images.githubusercontent.com/304786/184516340-b8d8d67e-0f4a-4839-a469-bfc4d89094fc.png)
   
   @sman-81 I guess CSV-301 could be the first added to 2.0.0. We can monitor 
new code, making sure it uses the new API and don't introduce new warnings. But 
not much else we can do until 2.0.0 I reckon.




Issue Time Tracking
-------------------

    Worklog Id:     (was: 800448)
    Time Spent: 1.5h  (was: 1h 20m)

> Fix deprecation warnings in unit tests
> --------------------------------------
>
>                 Key: CSV-301
>                 URL: https://issues.apache.org/jira/browse/CSV-301
>             Project: Commons CSV
>          Issue Type: Improvement
>    Affects Versions: 1.9.0
>            Reporter: Markus Spann
>            Priority: Trivial
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> Fix deprecation warnings in unit tests of the project.
> The project has a large number of deprecation warnings in unit tests. Use 
> updated API in these tests.
> Tests should keep up-to-date with the API, they often serve as a blueprint 
> for how to use functionality.
> I will provide a pull request shortly.



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

Reply via email to