[
https://issues.apache.org/jira/browse/MPLUGINTESTING-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17904049#comment-17904049
]
Harald Aamot commented on MPLUGINTESTING-72:
--------------------------------------------
Hi [~elharo] ,
thanks for checking back on this and lining out why you closed the issue.
Can you please explain what you mean with individual release?
This project only has alpha releases for Maven 4.x and the 3.x release line has
no release with JUnit5 support.
JUnit4 is reaching end of life and many projects move to JUnit5. SO every
project having maven plugin tests written in JUnit4 is unable to move to JUnit5
because of this missing feature in the maven-plugin-testing-harness.
I do not see any individual wish here but a very pressing feature request.
Best of all, the feature is already there, but not released.
So either offer a non-alpha 4.x release or allow me to further drive the 3.4.0
release.
Does that make sense?
> Release 3.4.0
> -------------
>
> Key: MPLUGINTESTING-72
> URL: https://issues.apache.org/jira/browse/MPLUGINTESTING-72
> Project: Maven Plugin Testing
> Issue Type: Wish
> Reporter: Samael Bate
> Priority: Major
> Fix For: 3.4.0
>
>
> the master branch is passing all builds. There hasn't been a release since
> 2014. What's the reasoning for not publishing a new release? There are
> numerous dependency updates as well as documentation fixes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
