Google Git
Sign in
chromium / external / mockito / mockito / refs/tags/v5.14.2
commit78348597236d54a84843f454936b8440b006f773[log] [tgz]
authorBrice Dutheil <brice.dutheil@gmail.com>Tue Oct 15 12:56:58 2024
committerGitHub <noreply@github.com>Tue Oct 15 12:56:58 2024
tree7f81d2c4b5c48b491fef856fbfe6dcf5bf22d78d
parent297d147cce8eeab1c43a0d3b7b2645464c7d2750 [diff]
Update `nexusPublishing` to use project.group(#3470)

This broke when we moved the core sources into
the `mockito-core` subproject.

See https://github.com/gradle-nexus/publish-plugin/blob/v2.0.0-rc-1/src/main/kotlin/io/github/gradlenexus/publishplugin/NexusPublishExtension.kt#L38-L40

Also, tweak the nexus `repositoryDescription` for the same reason.

Fixes #3466
1 file changed
tree: 7f81d2c4b5c48b491fef856fbfe6dcf5bf22d78d
  1. .github/
  2. config/
  3. doc/
  4. gradle/
  5. mockito-bom/
  6. mockito-core/
  7. mockito-extensions/
  8. mockito-integration-tests/
  9. .checkstyle
  10. .editorconfig
  11. .gitattributes
  12. .gitignore
  13. build.gradle
  14. check_reproducibility.sh
  15. gradle.properties
  16. gradlew
  17. gradlew.bat
  18. LICENSE
  19. README.md
  20. SECURITY.md
  21. settings.gradle.kts
README.md

Most popular mocking framework for Java

CI Coverage Status MIT License

Release Notes Maven Central Javadoc

Current version is 5.x

Still on Mockito 1.x? See what's new in Mockito 2! Mockito 3 does not introduce any breaking API changes, but now requires Java 8 over Java 6 for Mockito 2. Mockito 4 removes deprecated API. Mockito 5 switches the default mockmaker to mockito-inline, and now requires Java 11. Only one major version is supported at a time, and changes are not backported to older versions.

Mockito for enterprise

Available as part of the Tidelift Subscription.

The maintainers of org.mockito:mockito-core and thousands of other packages are working with Tidelift to deliver commercial support and maintenance for the open source dependencies you use to build your applications. Save time, reduce risk, and improve code health, while paying the maintainers of the exact dependencies you use. Learn more.

Development

Mockito publishes every change as a -SNAPSHOT version to a public Sonatype repository. Roughly once a month, we publish a new minor or patch version to Maven Central. For release automation we use Shipkit library (http://shipkit.org), Gradle Nexus Publish Plugin. Fully automated releases are awesome, and you should do that for your libraries, too! See the latest release notes and latest documentation. Docs in javadoc.io are available 24h after release. Read also about semantic versioning in Mockito.

Older 1.x and 2.x releases are available in Central Repository and javadoc.io (documentation).

More information

All you want to know about Mockito is hosted at The Mockito Site which is Open Source and likes pull requests, too.

Want to contribute? Take a look at the Contributing Guide.

Enjoy Mockito!

Need help?

How to develop Mockito?

To build locally:

 ./gradlew build

To develop in IntelliJ IDEA you can use built-in Gradle import wizard in IDEA. Alternatively generate the importable IDEA metadata files using:

 ./gradlew idea

Then, open the generated *.ipr file in IDEA.

How to release new version?

  1. Every change on the main development branch is released as -SNAPSHOT version to Sonatype snapshot repo at https://s01.oss.sonatype.org/content/repositories/snapshots/org/mockito/mockito-core.
  2. In order to release a non-snapshot version to Maven Central push an annotated tag, for example:
git tag -a -m "Release 3.4.5" v3.4.5
git push origin v3.4.5
  1. At the moment, you may not create releases from GitHub Web UI. Doing so will make the CI build fail because the CI creates the changelog and posts to GitHub releases. We'll support this in the future.