-
Notifications
You must be signed in to change notification settings - Fork 179
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
Could not find spek:spek-runtime:2.0.16 #964
Comments
In 2.0.16 publishing was moved to Maven Central due to bintray being shutdown. Do you have |
Yes, I have. |
Ahh wait, |
My declared dependencies.
Works perfectly until the change to 2.0.16 |
Can you setup a sample project that replicates the issue? |
Unfortunately, no, sorry.
The dependency really comes from spek-runner-junit5 |
What gradle version are you using? |
Btw, for 2.0.15 you're right, it depends on
|
I use Gradle v7.0-rc-2 |
I have the same or a similar problem with atrium (using gradle 6.7)
https://github.com/robstoll/atrium/pull/869/checks?check_run_id=2355507816 |
My guess it has something to do with not publishing the |
Interesting, bintray's publish plugin ignored gradle's module metadata files when publishing so it wasn't present in |
@DmitriyZaitsev @robstoll I suggest to use |
Good, I am actually still on 2.0.12 because of #927. Any chance you fix this as well? Can I help somehow? |
Ahh, totally forgot about that issue. @sh-soltanpour is going to look at it. |
* Bump spek-runner-junit5 from 2.0.8 to 2.0.16 Bumps [spek-runner-junit5](https://github.com/spekframework/spek) from 2.0.8 to 2.0.16. - [Release notes](https://github.com/spekframework/spek/releases) - [Changelog](https://github.com/spekframework/spek/blob/2.x/docs/breaking-changes.md) - [Commits](spekframework/spek@2.0.8...2.0.16) --- updated-dependencies: - dependency-name: org.spekframework.spek2:spek-runner-junit5 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]> * Roll back to 2.0.15 because of spekframework/spek#964 Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Basset, Justin <[email protected]>
when will 2.0.17 be released? |
@rburgst it is out already. |
Hm, its not listed on the github releases |
* Bump spek-runner-junit5 from 2.0.8 to 2.0.16 Bumps [spek-runner-junit5](https://github.com/spekframework/spek) from 2.0.8 to 2.0.16. - [Release notes](https://github.com/spekframework/spek/releases) - [Changelog](https://github.com/spekframework/spek/blob/2.x/docs/breaking-changes.md) - [Commits](spekframework/spek@2.0.8...2.0.16) --- updated-dependencies: - dependency-name: org.spekframework.spek2:spek-runner-junit5 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]> * Roll back to 2.0.15 because of spekframework/spek#964 Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Basset, Justin <[email protected]>
* Bump spek-runner-junit5 from 2.0.8 to 2.0.16 Bumps [spek-runner-junit5](https://github.com/spekframework/spek) from 2.0.8 to 2.0.16. - [Release notes](https://github.com/spekframework/spek/releases) - [Changelog](https://github.com/spekframework/spek/blob/2.x/docs/breaking-changes.md) - [Commits](spekframework/spek@2.0.8...2.0.16) --- updated-dependencies: - dependency-name: org.spekframework.spek2:spek-runner-junit5 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]> * Roll back to 2.0.15 because of spekframework/spek#964 Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Basset, Justin <[email protected]>
I started getting this error message after an update from 2.0.15 -> 2.0.16, which is weird as I see that that the latest available version of spek-runtime here is 2.0.0.
The text was updated successfully, but these errors were encountered: