Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: add merged jacoco report #271

Closed

Conversation

olegshestakov
Copy link

fix #143

@@ -186,6 +202,7 @@ configure(subprojects) { project ->
// dependencies that are common across all java projects
dependencies {
compile "io.projectreactor:reactor-core:$reactorCoreVersion"
compile 'org.jacoco:org.jacoco.agent:0.8.3'
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we've never had to add the agent nor even the core jars in our projects before. can you clarify why this is needed?

Comment on lines +98 to +101
apply plugin: 'jacoco'
repositories {
mavenCentral()
}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why add this to this particular block? apply plugin: 'jacoco' above should be enough

@@ -27,11 +27,13 @@ buildscript {
classpath 'org.springframework.build.gradle:propdeps-plugin:0.0.7'
classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:${kotlinVersion}"
classpath 'biz.aQute.bnd:biz.aQute.bnd.gradle:4.1.0'
classpath "org.jacoco:org.jacoco.core:0.8.3"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same as for agent, I don't believe we usually add core jacoco classpath

}
}

plugins {
id "com.jfrog.artifactory" version "4.15.2" apply false
id 'jacoco'
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should this be apply false if you're applying the plugin in each subproject ?

@simonbasle
Copy link
Member

@olegshestakov I've just reworked and updated the build, including a bump to Gradle 7.4. this could remove the need for explicitly depending on jacoco 0.8.3

@simonbasle simonbasle added for/user-attention This issue needs user attention (feedback, rework, etc...) status/on-hold labels Feb 18, 2022
@simonbasle simonbasle added status/declined We feel we shouldn't currently apply this change/suggestion and removed status/on-hold labels Jun 17, 2022
@simonbasle simonbasle closed this Jun 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
for/user-attention This issue needs user attention (feedback, rework, etc...) status/declined We feel we shouldn't currently apply this change/suggestion
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Export Code Coverage
2 participants