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

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.

1 answer

0 votes

See answer to your first question

Suggest an answer

Log in or Sign up to answer
Community showcase
Asked Thursday in Jira Ops

I'm John Allspaw, Ask Me Anything about incident analysis and postmortems

I'm John Allspaw, co-founder of   Adaptive Capacity Labs, where we help teams use their incidents to learn and improve. We bring research-driven methods and approaches to drive effective inciden...

5,416 views 21 17
View question

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you