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 Join to answer
Community showcase
Teodora [Botron]
Published Thursday in Marketplace Apps

Jira Inferno: The Nine Circles of Jira Administration Hell

If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...

415 views 1 13
Read article

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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot