We are migrating our build tools to another location (as part of closing this office). As such, we let our license lapse. This was not a problem until today when the new version of clover auto loaded and now our maven builds fail because that new version won't execute because the license expired. This is unexpected and, frankly, really stupid. It was working fine with the old version, it should not have autoloaded a version that it couldn't use - it broke our builds. How do I get back to a version that works? ie 3.1.4 was working fine, but 3.1.5 refuses to work.
You should explicitly specify a version number you want to use, for example:
<plugin> <groupId>com.atlassian.maven.plugins</groupId> <artifactId>maven-clover2-plugin</artifactId> <version>3.1.4</version> </plugin>
Typically it's enough to specify it in top-level pom only.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.