Status of intellij-coverage github project

Answered
Avatar
Permanently deleted user
Created

Is this the right forum to discuss the intellij-coverage project[1]? I can't seem to find anything more suitable.

I'm interested in contributing to intellij-coverage (eg converting its build from Ant to Maven, adding tests for coverage of Kotlin code, creating a Maven plugin to work with it), but before I put in too much work, I want to make sure my changes would be considered.

I'm a bit concerned about the status of intellij-coverage. I can see that it still gets updates occasionally, but this community pull request[2] looks pretty reasonable to me, yet it apparently hasn't received any attention in the 21 months since it was created. I guess it slipped through the cracks.

Is there a process for reviewing and processing pull requests in this project? 

 

[1] https://github.com/JetBrains/intellij-coverage

[2] https://github.com/JetBrains/intellij-coverage/pull/1/

 

Thanks,

 

Sean.

Votes

0

Share

2 comments
Avatar
Anna Kozlova
Created

Hi Sean,

maven/gradle plugins are planned but we always postpone it, sorry. Converting from ant to maven would mean that we would have to change our CI integration so what is the idea behind conversion? (Given that the project depends on exactly one library) I don't suggest to create new projects with ant but for migration I'd like to see reasons behind.

Thanks,

Anna

0
Avatar
Permanently deleted user
Created

Hi Anna,

Well, in general I'd say using a reasonably modern build system is a must for any open source project which wants community contributions, but more specifically:

  1. intellij-coverage already has 8 dependencies as jars in the repo, with no easy way to see what versions they are (eg versions in the filenames).
  2. To add Kotlin test cases will require adding another test dependency on kotlin-compiler-embeddable. I've already got a basic Kotlin test case to compile in the intellij-coverage project (despite the lack of docs for kotlin-compiler-embeddable), although I haven't yet succeeded in reproducing the problem I was seeing. [1]
  3. I'd like to try writing a Maven plugin myself (compiled as a Maven project), and for that I need a dependency on the coverage jars, which means I need the coverage jars as Maven artifacts. Publishing the coverage jars to Maven will be much, much easier if intellij-coverage is switched to Maven (or Gradle) than trying to do it in Ant (especially in view of #1 above).

Regards

Sean.

[1] My nascent Maven plugin initially tries to convert intellij-coverage files (.ic) into cobertura.xml files for use with Cobertura-compatible tools, but in some cases the package name appears twice in the classname (I can see it in a hex editor). It only seems to happen with Kotlin files which have inlined functions used in another file. So far I can't reproduce it in a unit test. 

0

Please sign in to leave a comment.