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

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

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

   >omg ... are you forced to do in this way by some set of conventions?
   
   @garydgregory might have a better explanation. I remember seeing that before 
I joined ASF. I also remember reading about it somewhere. I thought it was the 
Commons Wiki, but I couldn't find, I think:
   
   - https://cwiki.apache.org/confluence/display/COMMONS/MavenGroupIDChange
   - https://cwiki.apache.org/confluence/display/COMMONS/MavenAndClasspath
   
   Maybe we should make this information more visible to contributors.
   
   >The deprecation warnings will be addressed while removing old API and old 
tests in a new major release.
   >We can close my PR - no problem at all. The work is easily recreated when 
releasing.
   
   Thanks for understanding it! Closing the issue.
   
   > Again, thanks for your thoughts and feedback - have a great week.
   
   Thanks again and have a great week too @sman-81 !




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

    Worklog Id:     (was: 800535)
    Time Spent: 1h 50m  (was: 1h 40m)

> 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: 1h 50m
>  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