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

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

                Author: ASF GitHub Bot
            Created on: 30/Sep/19 23:00
            Start Date: 30/Sep/19 23:00
    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-536786593
 
 
   > Please try to get this to work with JaCoCo, we cannot loose this feature 
for our site.
   
   @garydgregory as I noted, as far as I can see, the JaCoCo report is broken 
regardless of this PR (the master build I linked to has a bunch of the same 
errors).
   The project reports section on the site 
(https://commons.apache.org/proper/commons-io/project-reports.html) doesn't 
have a JaCoCo report (unlike, e.g., Commons Lang), unless it's located 
somewhere else and I'm missing something basic.
 
----------------------------------------------------------------
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: 320961)
    Time Spent: 1h 40m  (was: 1.5h)

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