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

Task jacocoIntegrationTest is skipped if there is no test folder #479

Open
Woehni opened this issue May 20, 2021 · 3 comments
Open

Task jacocoIntegrationTest is skipped if there is no test folder #479

Woehni opened this issue May 20, 2021 · 3 comments
Assignees
Labels
bug Something isn't working

Comments

@Woehni
Copy link

Woehni commented May 20, 2021

If integrationTest is the only test module in the project then the task jacocoIntegrationTestReport is skipped.

Just by adding the empty folder structure test/kotlin the task will be executed.

In contrast to this the task integrationTestReport is executed as expected independent on the existence of the test module

This issue exists with version 0.45.0.

If anything is missing in my description, please get back to me. This is my first issue report on GitHub. :)

@aalmiray aalmiray self-assigned this May 20, 2021
@aalmiray aalmiray added the bug Something isn't working label May 20, 2021
@aalmiray
Copy link
Collaborator

Can you tell me which Kotlin plugins you have applied to the build? Please post the output of invoking gradle plugins. Thanks!

@Woehni
Copy link
Author

Woehni commented May 20, 2021

Total plugins: 22

plugin 0:
    id: lifecycle-base
    version: 6.8.3
    implementationClass: org.gradle.language.base.plugins.LifecycleBasePlugin
 
plugin 1:
    id: base
    version: 6.8.3
    implementationClass: org.gradle.api.plugins.BasePlugin
 
plugin 2:
    id: org.kordamp.gradle.base
    version: 0.45.0
    implementationClass: org.kordamp.gradle.plugin.base.BasePlugin
    enabled: true
 
plugin 3:
    id: reporting-base
    version: 6.8.3
    implementationClass: org.gradle.api.plugins.ReportingBasePlugin
 
plugin 4:
    id: jacoco
    version: 6.8.3
    implementationClass: org.gradle.testing.jacoco.plugins.JacocoPlugin
 
plugin 5:
    implementationClass: org.kordamp.gradle.plugin.jacoco.JacocoPlugin
 
plugin 6:
    implementationClass: io.spring.gradle.dependencymanagement.DependencyManagementPlugin
 
plugin 7:
    id: help-tasks
    version: 6.8.3
    implementationClass: org.gradle.api.plugins.HelpTasksPlugin
 
plugin 8:
    id: build-init
    version: 6.8.3
    implementationClass: org.gradle.buildinit.plugins.BuildInitPlugin
 
plugin 9:
    id: wrapper
    version: 6.8.3
    implementationClass: org.gradle.buildinit.plugins.WrapperPlugin
 
plugin 10:
    implementationClass: org.openapitools.generator.gradle.plugin.OpenApiGeneratorPlugin
 
plugin 11:
    implementationClass: org.kordamp.gradle.plugin.integrationtest.IntegrationTestPlugin
 
plugin 12:
    implementationClass: org.springframework.boot.gradle.plugin.SpringBootPlugin
 
plugin 13:
    id: jvm-ecosystem
    version: 6.8.3
    implementationClass: org.gradle.api.plugins.JvmEcosystemPlugin
 
plugin 14:
    implementationClass: org.gradle.api.plugins.JavaBasePlugin$Inject
 
plugin 15:
    id: java
    version: 6.8.3
    implementationClass: org.gradle.api.plugins.JavaPlugin
 
plugin 16:
    implementationClass: org.jetbrains.kotlin.gradle.scripting.internal.ScriptingKotlinGradleSubplugin
 
plugin 17:
    implementationClass: org.jetbrains.kotlin.gradle.scripting.internal.ScriptingGradleSubplugin
 
plugin 18:
    implementationClass: org.jetbrains.kotlin.gradle.plugin.KotlinPluginWrapper
 
plugin 19:
    implementationClass: org.jetbrains.kotlin.allopen.gradle.AllOpenGradleSubplugin
 
plugin 20:
    implementationClass: org.jetbrains.kotlin.allopen.gradle.SpringGradleSubplugin
 
plugin 21:
    id: kotlin.kotlin-dsl-project
    version: 6.8.3
    implementationClass: org.gradle.kotlin.dsl.provider.plugins.KotlinScriptBasePlugin

It is a multiproject setup. I just posted the plugins for the afflicted subproject.

@aalmiray
Copy link
Collaborator

Well that's strange. I've create both a single and a multi project build with just Java projects and have not encountered the problem, yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants