-
Notifications
You must be signed in to change notification settings - Fork 42
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
Publish a new release of junit-interface? #94
Comments
@szeiger it looks like novocode.com is your domain so presumably you're the one who would make a release here since junit-interface is published under com.novocode? |
Friendly ping 🙂 |
I have not used sbt in many years. I'm not the right person to ask about this |
is there is a strong need to stay on com.novocode, or could we just move this to be published under a different org? perhaps that would be the path of least resistance here. (I can't afford to get too involved in this repo, as I've already got too many other things going, but I do have merge rights, so I can assist to some extent with getting things moving again) |
@unkarjedy might you be interested in taking over the publishing...? |
@SethTisue |
@eed3si9n is this repo a candidate for being published under some existing sonatype account you manage, or would @unkarjedy need to publish under his own org? i know that you aren’t providing publishing to just anybody anymore, but I’m genuinely unsure whether you might still be open to hooking up certain core, widely used repos like this one |
Yea. This sounds like a good candidate to pick up. |
I've invited @ashawley and @unkarjedy to https://github.com/orgs/sbt/teams/junit-interface team. |
I just released junit-interface 0.12, 0.13, 0.13.1, and 0.13.2 corresponding to JUnit 4.12, 4.13, 4.13.1, and 4.13.2. |
junit-interface 0.11 was released over 6 years ago. Since then, various improvements have been pushed to this repo including 2018357 last year which provides some nice improvements to the test output. Would it be possible to publish a new release to maven?
The text was updated successfully, but these errors were encountered: