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

Tasks that are not supposed to be configured are beign configured #15935

Open
iherasymenko opened this issue Jan 25, 2021 · 2 comments
Open

Tasks that are not supposed to be configured are beign configured #15935

iherasymenko opened this issue Jan 25, 2021 · 2 comments
Labels
a:bug in:configuration-model lazy api, domain object container

Comments

@iherasymenko
Copy link

iherasymenko commented Jan 25, 2021

Expected Behavior

compileTestJava should not be configured

Current Behavior

compileTestJava is being configured

Context

Steps to Reproduce

build.gradle

plugins {
    id 'java'
} 

repositories {
    mavenCentral()
}

dependencies {
    implementation 'com.eclipsesource.minimal-json:minimal-json:0.9.5'
}

tasks.named('compileTestJava', JavaCompile) {
    println 'configuring compileTestJava'
}

tasks.named('compileJava', JavaCompile) {
    println 'configuring compileJava'
}

If I trigger the compileJava (gradlew compileJava) task, the compileTestJava task is also being configured. I.e. the console output will contain configuring compileJava and configuring compileTestJava.

If I remove the dependencies section, I can oversee the expected (In my opinion, of course) behavior. Only configuring compileJava is printed.

Your Environment

Gradle 6.8, Azul Zulu OpenJDK 15, Windows 10

Build scan URL:
https://scans.gradle.com/s/4esooetri7ksi - with the dependencies section
https://scans.gradle.com/s/fhivxvw7ivrks - without the dependencies section

@ljacomet ljacomet added the in:configuration-model lazy api, domain object container label Apr 19, 2021
@stale
Copy link

stale bot commented Apr 19, 2022

This issue has been automatically marked as stale because it has not had recent activity. Given the limited bandwidth of the team, it will be automatically closed if no further activity occurs. If you're interested in how we try to keep the backlog in a healthy state, please read our blog post on how we refine our backlog. If you feel this is something you could contribute, please have a look at our Contributor Guide. Thank you for your contribution.

@stale stale bot added the stale label Apr 19, 2022
@Vampire
Copy link
Contributor

Vampire commented May 5, 2022

Still the same with 7.4.2.

@stale stale bot removed the stale label May 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a:bug in:configuration-model lazy api, domain object container
Projects
None yet
Development

No branches or pull requests

4 participants