This message was deleted.

I'm not aware of such a service. I think you could use slf4j in your action, though.

But would that connect with the project’s logger settings?

So I have tested a little script and unfortunately it seems that the logger is not bound to the project logger, so logs are swallowed it seems 😞

Do you use process isolation or a different level? (you both)

my scrpt uses

noIsolation()

And there is no injectable logging service yet, no

test script:

buildscript {
    repositories {
        mavenCentral()
    }
    dependencies {
        classpath 'org.slf4j:slf4j-api:1.7.25'
    }
}

interface MyWorkParams extends WorkParameters {
    Property<String> getName()
}

abstract class SayHello implements WorkAction<MyWorkParams> {
    
    private static final Logger LOGGER = org.slf4j.LoggerFactory.getLogger(SayHello)
    
    void execute() {
        LOGGER.debug("Hello, {}!", getParameters().getName().get())
    }
}

abstract class SayHelloTask extends DefaultTask {
    @Inject
    abstract WorkerExecutor getWorkerExecutor()

    @TaskAction
    void execute() {
        workerExecutor.noIsolation()
            .submit(SayHello) {
                name.set("Cédric")
            }
    }
}

tasks.register("hello", SayHelloTask)

calling

hello

shows nothing

I mean, how else would a

WorkerAction

pass information to console/log which is compatible with the build’s logging settings? Sure I can use

println

but, … if so, what’s the point of logging APIs then?

Well, did you enable debug logging @melix? Otherwise it of course does not show anything.

I tried info, trace and debug

And did you enable the level?

no, because I'm looking for a log level which would bind to

lifecycle

so that it shows something like

println

The default logging level is LIFECYCLE

warn actually works

That log level is not a standard log level, it is only available with the Gradle own logger subclass

I know, but if you want to avoid

println

, you have to find one level which works 😄

Or you cannot use slf4j but have to use the Gradle logger

so, verified: •

info

-> logged if you run with

-i

•

warn

-> logged as lifecycle •

debug

-> logged if you run with

-d

Gradle used to log much more information by default, but at some point shifted more and more output to

--info

or below to not clutter the output with info logs and thus better see important messages like warnings and errors.

ah right. But at least shows something on the console.

Also don't forget

--quiet

;-)

logging in Gradle is a mess

Well, ..., yes

like no way to only log a single task type

Thanks. I chose

Logging.getLogger()

works too?

Yes, just tried it

interesting, I had no idea Gradle supported j.u.l

That's a Gradle class

correct, it’s

org.gradle.api.logging.Logging

Just what I suggested some messages above

ahhh, mixed with

Logger

.

TooManyLoggersException

It works fine as long as you have the Gradle APIs available and write Gradle specific code.

My gut feeling tells me when there are too many options, go with the Gradle flavor class, as this is the case. thanks @Vampire