Clover loaded new version which won't execute because of expired license

DaveT June 11, 2012

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.

2 answers

1 accepted

0 votes
Answer accepted
Marek Parfianowicz
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
June 11, 2012

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>

DaveT June 12, 2012

we don't currently have the clover plugin referenced in our poms. does that mean we have to add this to each pom?

Marek Parfianowicz
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
June 12, 2012

Typically it's enough to specify it in top-level pom only.

0 votes
DaveT June 14, 2012

that worked for us. Thank you!

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events