You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "andpab (via GitHub)" <gi...@apache.org> on 2023/02/16 19:58:24 UTC

[GitHub] [maven-surefire] andpab commented on pull request #571: [SUREFIRE-2121] JUnitException: Failed to parse version of junit:junit: 4.13.2

andpab commented on PR #571:
URL: https://github.com/apache/maven-surefire/pull/571#issuecomment-1433635709

   Definitely. The corresponding JIRA issue SUREFIRE-2121 can also be closed as Won't Fix.
   
   If you're in the process of cleaning up, the PR #493 can be closed as well. And the respective issue SUREFIRE-2039 can be closed as a duplicate of SUREFIRE-2032.
   
   The following issues have apparently been fixed according to the comments: 
   
   - SUREFIRE-2096 (fixed in 3.0.0-M8)
   - SUREFIRE-2094 (fixed in 3.0.0-M8)
   - SUREFIRE-2068 (fixed in 3.0.0-M7)
   
   There are also a couple of other issues that in my opinion can be closed as Won't Fix:
   
   - SUREFIRE-2120
   - SUREFIRE-2115


-- 
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.

To unsubscribe, e-mail: issues-unsubscribe@maven.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org