Clover open-sourcing FAQ
Atlassian Clover is now available as an open-source project. Effective April 11, 2017 Clover is no longer available for purchase or renewal.
Read the official announcement here: https://www.atlassian.com/blog/announcements/atlassian-clover-open-source
|Why are you open-sourcing Clover?|
Our company mission - to unleash the potential in every team - shapes the products we create today. A big part of this is delivering new features and improvements through continual updates and releases.
For many years Atlassian Clover has provided Java and Groovy developers a reliable source for code coverage analysis. This dependability has allowed us to focus our development efforts on delivering new features and improvements to our core offerings, including JIRA Software, Bitbucket, and others. All of this has lead to our decision to open source Clover, what we believe is the best way to give Clover the focus and attention it deserves.
Developers are ready and eager to contribute to Clover as they have with our other open-source projects including the IDE connectors and dozens of libraries. Although Clover is already a powerful code coverage tool we're excited to see what the community will do to make it thrive.
|Where can I download Clover and when can I begin to contribute?|
Effective April 11, 2017 source code for Clover is available for download at https://bitbucket.org/atlassian/clover. To begin running Clover as open source, you'll need to clone and compile locally. Open-source documentation for Clover is available here: https://atlassian-docs.bitbucket.io/. You can also discover contributions made by others in the forks dialog on Bitbucket.
For those needing to download a binary of Clover you can access all versions leading up to 4.1.2 in our downloads archive (note these will require a license key). Technical documentation for the last official Atlassian Clover release (4.1.2) will remain available on confluence.atlassian.com.
|I still have active maintenance on Clover, how does the open sourcing effect me?|
Official support for the latest release of Clover (4.1.2) will end on April 11, 2018. If your maintenance period ends after this date, you can expect to receive a refund equal to the time period extending beyond April 11, 2018.
Keep in mind that all Clover licenses are perpetual, which means you can use the last release for as long as you'd like. However in the future you might consider using the open-source version prepared by the community to access new features.
|Can I still renew or upgrade Clover?|
Renewals and upgrades of Clover are no longer available effective April 11, 2017. If you require an upgrade to a different license tier we recommend switching to the open-source version. Open-source Clover does not require a license tier and offers unlimited usage.
Clover source code is available for download at https://bitbucket.org/atlassian/clover. To begin running Clover as open source, you'll need to clone and compile locally. Open-source documentation for Clover is available here https://atlassian-docs.bitbucket.io/.
I switched to the open-source version of Clover but still have active maintenance on my old license. Can I receive support?
|Atlassian support is only valid for the licensed version of Clover. Official support for the latest Clover release (4.1.2) will end on April 11, 2018.|
|When will Atlassian stop supporting Clover?||Official support for our last release of Clover (4.1.2) will end April 11, 2018.|
|I just renewed or purchased Clover, can I get a refund?|
If you purchased after Feb 1st, 2017 and do not require official Atlassian support for Clover, you can request a refund of your commercial or academic license. Note that Atlassian will honor all support and maintenance contracts through April 11, 2018.
To request a refund/exchange please contact our Customer Advocates.
|I have a Clover license, do I need to migrate to another tool?|
No migration is required. Please bear in mind that license keys issued by Atlassian are perpetual, so you can use Clover as long as you want.
However, you may want to consider using the open-source version prepared by the community (if any are released) to get new features.
For additional questions or concerns, please contact us.