-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
What is the status of this project? #74
Comments
Hey @vasilmkd,
I plan to bring this plug in up-to-date in the coming weeks, so we can use it in the Play Framework. Also see #59 which I will take a look at then and merge and see what needs to be done. If you want to provide pull requests please do so. |
Thank you, this is very encouraging! I will let you start the work with merging the existing PRs, so that we don't start moving in potentially different directions. Then we'll take it from there. I will keep an eye out on the repository. |
I've set up release automation, and published:
and sent #87 for |
Hello 👋🏻 .
My intention with this question is only from a project management perspective. I do not wish to put any pressure on the developers of this project, nor do I expect or feel entitled to receive any new feature work or bug fixes.
I work on the Scala Plugin for IntelliJ IDEA team at JetBrains. We're currently using
junit-interface
to run the plugin tests. We're looking into moving on tosbt-jupiter-interface
in order to take advantage of JUnit 5. With the help ofjunit-vintage-engine
we would like to continue running our old tests without changes and write new tests using JUnit 5.While the test framework works in the simple cases, I'm quickly running into problems already mentioned in #41 and #54 some years ago.
I'm trying to evaluate whether it would be a good idea to start using
sbt-jupiter-interface
.From the outside, it feels like this project has been abandoned. Are there any plans to resume development? Is the project in need of more contributors?
Thanks in advance.
The text was updated successfully, but these errors were encountered: