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

ASF GitHub Bot logged work on IO-628:
-------------------------------------

                Author: ASF GitHub Bot
            Created on: 01/Oct/19 10:49
            Start Date: 01/Oct/19 10:49
    Worklog Time Spent: 10m 
      Work Description: mureinik commented on issue #97: IO-628: Migration to 
JUnit Jupiter
URL: https://github.com/apache/commons-io/pull/97#issuecomment-536980943
 
 
   > The build you point to 
https://travis-ci.org/apache/commons-io/jobs/591248951 is a Java 14-EA build, I 
do not think we need to worry that JaCoCo does not support Java 14-EA at this 
point because it shadows a version of ASM that does not support Java 14-EA.
   
   @garydgregory that's a good point, thanks. I originally overlooked that. I 
messed around with Travis CI a bit, and redid the last patch so JaCoCo is only 
disabled for the JDK EA build.
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


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

    Worklog Id:     (was: 321174)
    Time Spent: 4h  (was: 3h 50m)

> Migration Commons-IO to JUnit Jupiter
> -------------------------------------
>
>                 Key: IO-628
>                 URL: https://issues.apache.org/jira/browse/IO-628
>             Project: Commons IO
>          Issue Type: Task
>          Components: Utilities
>            Reporter: Allon Mureinik
>            Priority: Minor
>          Time Spent: 4h
>  Remaining Estimate: 0h
>
> Migrate the Commons IO project to the modern JUnit Jupiter framework (instead 
> of JUnit 4 which it currently uses) in order to make it easier to maintain 
> and for future contributors to participate.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to