The build publishes new version if specific criteria are met: all tests green, no 'ci skip release' used in commit message, see the build log for more information. Every new version is published to mockito/maven Bintray repository. New versions that Mockito team deems notable are additionally published to Maven Central and JCenter.
Dec 11, 2014 · I really don't see how usage of Verifications or StrictExpectations could be a problem in relation to @PostConstruct.In my example test, expectations needed by a @PostConstruct method are recorded in a @before method; you would never use "Verifications" there because it wouldn't make sense, and as for StrictExpectations, they are not meant to be used in a @before method, even if allowed. May 27, 2019 · This example uses the AEM project archetype 19 to generate a new AEM project, Junit 4 will be used as the testing framework, Mockito 2.27.0 will be used as the mocking framework, and AEM Mocks will be used to mock AEM objects and AEM API’s. What’s really great about the latest versions of AEM mocks, is that the setup is very minimal.