No additional dependency should be required. Mockito.mockStatic is part of mockito core. As far as I remeber you just have to add the file "org.mockito.plugins.MockMaker" in the folder "mockito-extensions" in your test resources root.
However if you really want to exclude the dependency of mockito from spring you can do so by adding an exclusion in your pom.xml dependency. An example of how to explicitly exclude a dependency of a library would look like this.
<dependency>
<groupId>jcifs</groupId>
<artifactId>jcifs</artifactId>
<version>1.3.17</version>
<exclusions>
<exclusion>
<groupId>javax.servlet</groupId>
<artifactId>servlet-api</artifactId>
</exclusion>
</exclusions>
</dependency>
Also be really carefull with using mockStatic. Always call close in the end or otherwise the staticMock will stay active in the Thread (across multiple unit tests).
Creates a thread-local mock controller for all static methods of the given class or interface. The returned object's MockedStatic.close() method must be called upon completing the test or the mock will remain active on the current thread.
Note: We recommend against mocking static methods of classes in the standard library or classes used by custom class loaders used to executed the block with the mocked class. A mock maker might forbid mocking static methods of know classes that are known to cause problems. Also, if a static method is a JVM-intrinsic, it cannot typically be mocked even if not explicitly forbidden.
See examples in javadoc for Mockito class
Params:
classToMock – class or interface of which static mocks should be mocked.
defaultAnswer – the default answer when invoking static methods.
Returns:
mock controller