As a very new contributor, how can I debug the internals of a Gradle bin file? For example, I want to be able to set breakpoints within the subproject(s) that the issue involves

For my own problem solving and learning I am trying to log from Gradle itself, currently a quick test via

Logging.getLogger(DefaultConfiguration.class).log(<http://LogLevel.INFO|LogLevel.INFO>, "This is a test");

I then rebuild the Gradle distro, as described in CONTRIBUTING.md, via

./gradlew install -Pgradle_installPath=/tmp/gradle-test

and use that distribution in my test project. I run that with

/tmp/gradle-test/bin/gradle --console verbose --debug <some task>

But I don't see any logging messages that I added. Granted, it could be the code path I am logging from is not taken but I just wanted to check that I'm doing the logging above (via

.getLogger()

) correctly before diving in too deep. I can't find any docs about how to do logging from within Gradle itself

Hi ! I am trying to build a local build from one of the previous revision tags as mentioned in the Contribution.md. But I am facing some errors that I am not aware how to fix at the moment. Can anyone please help me with what I am doing wrong? These are the logs i get whenever i try to run commands.

There seem to be two problems: 1. That revision uses some nightly for wrapper that doesn’t exist anymore. I suggest you use some “close enough” released version, maybe 6.8 or some 6.7.x (released versions can be found here https://services.gradle.org/distributions/) 2. Kotlin-dsl cant be found in

kotlin-eap

repo or Gradle plugin repo for some reason. Maybe you should add some other repo to build logic or smth like that, not sure Fun with remote resources 🙂

When apply dependency verification to our builds the question came up if certain types of checksums could be forbidden. that would ease our process quite a bit and might be a good additional feature. Does this sound as it would make sense to you to make allowed checksum types configurable?

If you are looking to do some contributing this month (and want some swag) we just pushed all the Configuration Cache issues to the public board. https://github.com/orgs/gradle/projects/43/views/1

What kind of specs are needed to work with intelliJ to contribute to Gradle? I am making changes to the snippets to make it configuration cache compatible and the Kotlin code completion/highlighting doesn't work on my machine. Wondering if this is a memory limitation or some quirk with intelliJ?

I’m taking a stab at issue 21803 of Configuration Cache Hackathon. However, I’m unable to reproduce the test failures. I have gone through the workflow & FAQ documentation and I see the following log:

0 problems were found storing the configuration cache.

See the complete report at file:///Users/myusername/CD/gradle/build/reports/configuration-cache/5ivt49antbai1kfb8a5y3bxrs/3b6067qhgwn5n39a8z4ha05pg/configuration-cache-report.html

I am looking to add a few examples to the Gradle user guid. Am I allowed to contribute here as a non-gradle member ? Ref: https://docs.gradle.org/current/userguide/userguide.html

Hi! Any suggested issues for new contributors?

Having a little difficulty understanding what these failed checks in CI mean. Can someone suggest what to look at to fix these? Regarding this PR below https://github.com/gradle/gradle/pull/21437.

Who can help to see or review whether this PR meets the requirements ? thanks. https://github.com/gradle/gradle/pull/23097 and https://github.com/gradle/gradle/pull/23102

Any reason to force JDK 11 to develop on the repo?

Any chance to get this tiny fix (that helps to provision the GraalVM toolchain) to Gradle 8.0 still? https://github.com/gradle/gradle/pull/23470

Hey all, first time contributor here. I opened up a PR to add progress reporting to Gradle’s plain mode: https://github.com/gradle/gradle/pull/22541 Would love to get a first pass review. Feel free to redirect me to a better channel to talk code review

Hey, what is the task name to add binary changes to the binary changes files to pass the binary checker task? I didn't find this task name in the CONTRIBUTING.md?

Am I the only one that experiences frequent issues trying to open Gradle source in IntelliJ? Seems like every time I come back to this project there's some new issue for me to battle. It's extremely frustrating when all you want to do is investigate something or perhaps look into the possibility of making a contribution. I'll be honest, it can drive me to immediately give up and move on to other projects/ideas because I don't want to spend time debugging it. Today's mishap:

Cannot locate tasks that match ':pineapple:classpathManifest' as project 'pineapple' not found in root project 'gradle'.

Proposal: JvmComponentDependencies Factory I'm currently working on a plugin that could benefit from having a dependency DSL similar to the jvm test suites plugin. After looking at the implementation it seems there isn't really a good public API friendly way of creating instances for

JvmComponentDependencies

. I could use

DefaultJvmComponentDependencies

directly like the test suites plugin does, but unfortunately that exposes me to changes in the constructor. For example, a configuration was added in 7.5, so I would need to handle the differing required constructor args. Solvable, but not ideal of course. Is there any appetite for adding a factory method to

SourceSet

that creates an instance, or some variation on that idea? The test suite and my plugin could both call the factory method for the applicable source set and would not need to worry about the internal details of the required configurations.

SourceSet

configurations and

DefaultJvmComponentDependencies

can remain in sync with the configuration conventions of the time and the plugins don't really need to care (at least not from a dependency declaration perspective). The plugins automatically get whatever the current support is for configuring the dependencies of a source set. Thoughts on if there are already plans in motion or if this is something worth pursuing?

My PR has been open for more than month without feedback. Can I get anyone to look at it? It's about docs only... https://github.com/gradle/gradle/pull/24847

Hey folks, This channel was the initiative of our former Developer Advocate. With Gradle now back to looking for a dev advocate, the rest of the team has limited bandwidth to interact here. Be aware that answers may take a while from the Gradle team. We will update once we have a sustainable plan for handling contributions.