Details
-
Suggestion
-
Resolution: Won't Fix
-
None
Description
Hi Folks,
Thanks for your feedback, we regularly review your requests in order to schedule the improvements that our customers highlight as most important and useful.
After surveying the Clover customer base, we believe that the main use cases of Clover are satisfied by its current feature set. Due to this, we have decided to close this feature request as we are not planning to address this in the near future.
For any questions or queries, please feel free to comment on this issue, we will get back to you in a timely manner.
Regards,
Josh Devenny
Atlassian Product Management
Status update 18.06.2014:
I've made a spike for this. It's feasible and I've got a working prototype, but it needs a lot of polishing.
Tasks:
perform spike to estimate complexity
solve problem with concurrent updates of clover.db (first is IDE/JPS builder process for Java code, second is Groovyc AST transformer) - maybe we could use two databases instead and merge them after the build in memory for reporting? it would require change in Settings > Clover window as well
serialize Clover configuration to instrumentation.ser (initstring etc to be used by Clover Groovy AST Transformer)
serialize inclusion/exclusion patterns for *.groovy files into the instrumentation.ser (files to be instrumented by Clover)
integrate with IDEA's Groovy plugin (e.g. via GroovyBuilderExtension)
pick Clover AST Transformer by groovyc process (META-INF/services)
handle build started/finished events for Groovy-based projects
show Groovy classes in the Cloverage view
handle stub generation by groovyc?
syntax highlighting for Groovy code (in editor tab)
check integration with Groovy test runner / Spock test runner
check instrumentation of mixed Java/Groovy projects (esp. compilation of Java sources from groovyc)
handle compilation of Groovy code triggered from other IDEA plug-ins, such as: Grails, Gradle, Griffon
check report generation (HTML, XML, PDF) launched from IDEA
