I have released version 1.2 of the mutation-analysis-plugin this morning under LGPLv3, download+source available on github: mutation-analysis-plugin
The previous releases have been developed under a commercial license/closed source of my company. But since the business outcome was below expectation, I decided to open source it, so that more people can benefit from it’s features and hopefully I’ll get feedback (bugs, feature requests…) from a broader project usage.
Now to the more complicated aspects.
The plugin originated in an early fork (+3yrs) of the sonar-pitest plugin but ended up in a complete rewrite of the plugin. Version 1.2 is the 3rd release.
Now, both plugins have kind of overlap, with sonar-pitest offering “just” a subset of the mutation-analysis-plugin. Additional features are individual rules per mutant (including documentation), a set of additional metrics and (experimental) maven-multi-module support, and a built-in quality profile, but it offers no Kotlin support.
For me the question is now, how to proceed?
For one, I would like to see the plugin being listed in the market place, which makes it more visible and installation more convenient to a wider audience. As far as I’ve understood, the plugin must meet the requirements and has to undergo a check by SonarSource staff. So what would be the next step in that direction?
But I would also like to team up with the developer(s?) of the sonar-pitest plugin efforts as it doesn’t make much sense to me to have two separate plugins with overlapping functionality.
I’ve seen the ownership of the plugin went to Vinod Anandan, who is not yet in this forum, and @Brad Flood is occasionally pushing minor updates to the plugin.
My suggestion would be, to end the sonar-pitest plugin lifecycle with version 0.9 or have a final release of 1.0 or and then switch over to 1.2 of the mutation-analysis-plugin.
Any thoughts, questions or recommendations on this are much appreciated?