Repack the intellij-agent artifact to kover-jvm-agent #464
Assignees
Labels
Comments
shanshin
added
Feature
shanshin
added a commit
that referenced
this issue
Feb 26, 2024
User can use the JVM agent separately, with the name kover and without mentioning IntelliJ, as well as reduce the number of parameters and properties required to transfer to the agent. Now Kover Gradle Plugin uses kover-jvm-agent with the same version. To do this, the transfer of staging repositories was added to the functional tests. The common logic of publishing was also extracted into a separate convention plugin. Resolves #464
shanshin
added a commit
that referenced
this issue
Feb 26, 2024
User can use the JVM agent separately, with the name kover and without mentioning IntelliJ, as well as reduce the number of parameters and properties required to transfer to the agent. Now Kover Gradle Plugin uses kover-jvm-agent with the same version. To do this, the transfer of staging repositories was added to the functional tests. The common logic of publishing was also extracted into a separate convention plugin. Resolves #464
shanshin
added a commit
that referenced
this issue
Feb 27, 2024
User can use the JVM agent separately, with the name kover and without mentioning IntelliJ, as well as reduce the number of parameters and properties required to transfer to the agent. Now Kover Gradle Plugin uses kover-jvm-agent with the same version. To do this, the transfer of staging repositories was added to the functional tests. The common logic of publishing was also extracted into a separate convention plugin. Resolves #464
shanshin
added a commit
that referenced
this issue
Feb 29, 2024
User can use the JVM agent separately, with the name kover and without mentioning IntelliJ, as well as reduce the number of parameters and properties required to transfer to the agent. Now Kover Gradle Plugin uses kover-jvm-agent with the same version. To do this, the transfer of staging repositories was added to the functional tests. The common logic of publishing was also extracted into a separate convention plugin. Resolves #464 PR #550
|
Introduced in |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In the case where the
kover-cliis used for generating reports, users may need to perform on the fly instrumentation that will produce compatible results.Since
intellij-agenthas a versioning that differs from the version of Kover, it will be problematic for the user to choose the appropriate version.It can also confuse the use of dependencies from intellij, which is not explicitly related to Kover for the user.
Additionally, in the new artifact, we may pass parameters and system variables in a different form and with different names, more typical for Kover
The text was updated successfully, but these errors were encountered: