Joseph Woolf
07/22/2022, 5:14 AMFred Clausen
07/26/2022, 1:21 AMLogging.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 itselfDeTerminator
07/27/2022, 2:15 AMAnze Sodja
07/27/2022, 7:47 AMkotlin-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 🙂René
08/01/2022, 8:59 AMAmanda
09/01/2022, 7:26 PMSid B
09/06/2022, 10:35 PMVinay Potluri
09/11/2022, 9:16 PM0 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
Vinay Potluri
10/02/2022, 7:14 PMGabriel Feo
10/11/2022, 9:52 PMDeTerminator
11/30/2022, 2:08 PMLi Jimmy
12/14/2022, 12:04 PMMartin
12/19/2022, 2:38 PMSebastian Schuberth
01/11/2023, 4:41 PMKevin Mark
01/27/2023, 7:00 PMPhilip W
05/05/2023, 10:00 AMChris Doré
05/24/2023, 12:21 PMCannot locate tasks that match ':pineapple:classpathManifest' as project 'pineapple' not found in root project 'gradle'.
Chris Doré
05/24/2023, 4:56 PMJvmComponentDependencies
. 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?Sebastian Schuberth
05/25/2023, 1:36 PMLouis Jacomet
05/30/2023, 4:02 PM