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
mockk-1.12.6.jar from MavenCentral is empty #884
Comments
Also e.g. https://repo.maven.apache.org/maven2/io/mockk/mockk-jvm/1.12.6/mockk-jvm-1.12.6.pom is missing completely. |
An other strange thing is that https://repo.maven.apache.org/maven2/io/mockk/mockk-jvm/1.12.6/ does exist, however https://repo.maven.apache.org/maven2/io/mockk/mockk-jvm/1.12.5/ does not |
Definitely something wrong with the new buildfiles introduced lately, my bad, going to fix this. Sorry for the inconvenience. |
So, apparently switching to the multiplatform build introduced the It's being published on sonatype, but then it does not go to maven central. Looking into it, it should just be a matter of telling sonatype to publish all modules to maven central. |
Previously the mockk/mockk/jvm/build.gradle.kts Lines 41 to 43 in 1d1e6a8
Now the naming is handled by the Kotlin Multiplatform project, which publishes a common |
Yep I figured so, so now the It shouldn't be an issue, if only mockk-jvm was published on maven central :) |
Added a comment here https://issues.sonatype.org/browse/OSSRH-35388 to see if it's an issue with sonatype. |
Idk if this is related, but was the |
Ok i got to publish I'd like some of you to at least give it a try before publishing a release on GitHub, can you please try upgrading to Tagging folks like @qoomon and @aSemy in case they can provide feedback |
1.12.7 is working fine for me @Raibaz, now artifact |
@Raibaz LGTM, too! |
It looks good for the mockk-android artifact as well
|
|
Ok, I released 1.12.7, thanks a lot everyone for the feedback and the patience! |
This fixes a deployment issue [1] with version 1.12.6 [2]. [1]: mockk/mockk#884 [2]: https://github.com/mockk/mockk/releases/tag/1.12.6 Signed-off-by: Sebastian Schuberth <sschuberth@gmail.com>
This fixes a deployment issue [1] with version 1.12.6 [2]. [1]: mockk/mockk#884 [2]: https://github.com/mockk/mockk/releases/tag/1.12.6 Signed-off-by: Sebastian Schuberth <sschuberth@gmail.com>
To me it's still not resolved. mockk-1.12.7.jar is still empty. Do I have to switch to mockk-jvm dependency instead? cf. #891 |
At least Gradle picks the JVM artifact automatically, and I also can confirm our project to build fine with MockK 1.12.7. |
If you're using Maven, can you try changing <dependency>
<groupId>io.mockk</groupId>
<!-- <artifactId>mockk</artifactId> -->
<artifactId>mockk-jvm</artifactId>
<version>${mockk.version}</version>
</dependency> |
@aSemy yes code compiles again when I switch to mockk-jvm. However during test execution I am now getting the following exceptions:
Is this a separate issue? |
@stefanzilske I'm seeing something similar after trying to upgrade from
|
Seeing |
Please remove sections wisely
Below information is actually needed to make all the process of fixing faster.
Choose main points. Don't blindly follow this as a set of rules.
Don't waste much time. Usually, the main thing is to have a good reproducible minimal code.
Prerequisites
Please answer the following questions for yourself before submitting an issue.
Expected Behavior
Upgrading to mock 1.12.6 should contain no breaking changes.
Current Behavior
The jar downloaded from Maven Central is empty, it contains only META-INF directory: https://search.maven.org/artifact/io.mockk/mockk/1.12.6/jar
Context
Please provide any relevant information about your setup. This is important in case the issue is not reproducible except for under certain conditions.
The text was updated successfully, but these errors were encountered: