[
https://issues.apache.org/jira/browse/GROOVY-11788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18070145#comment-18070145
]
ASF GitHub Bot commented on GROOVY-11788:
-----------------------------------------
paulk-asert commented on PR #2412:
URL: https://github.com/apache/groovy/pull/2412#issuecomment-4165610089
@eric-milles As per the "Bumping junit jupiter to version 6" email on the
dev list, this was more about maintaining a convenience for users of just
having to have groovy-test-junit6 as their dependency. Also, it is flagging
that there will be changes across the different Jupiter versions. For instance,
Jupiter 6 supports "Native Kotlin suspend Tests". Assuming we go ahead with
async/await, I wanted to see whether a similar capability for Groovy
async/await made sense. If it did, targeting Jupiter 6 would seem the right
target. Also, we know JUnit 3/4 is now deprecated. If it is removed in Jupiter
7, we might again want changes for a groovy-test-junit7.
Having said all that, this seems to be one of those "could go either way"
type decision points. Hence the email.
> Bump JUnit to 6.0.3
> -------------------
>
> Key: GROOVY-11788
> URL: https://issues.apache.org/jira/browse/GROOVY-11788
> Project: Groovy
> Issue Type: Dependency upgrade
> Reporter: Daniel Sun
> Priority: Major
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
