This message was deleted.

Maybe you should not do that, but simply register one task instance per pair?

@Vampire not sure how to implement that. tasks are defined by the plugin, so the user can't just

tasks.getByName<MyPluginTask("secondConfig") { ...

...

The user can just register additional tasks if he likes or needs. Or you could provide some means like a function in an exetension to which you give the input and output that then register the additional task. Or a named domain object collection, like for example the Java plugin does. When you create or register a new

sourceSet

, the Java plugin automatically registers and wires compilation tasks for it. Or when you create or register a new test suite, the jvm test suite plugin registers new test tasks for it, and so on.

i think i like the function in the extension best. i guess that'd look like this, then:

tasks.getByName<MyPluginTask>("myplugin") {
    addConfig("foo") {
        inputDirectory = "$projectDir/src/main/xyz"
        outputDirectory = "$buildDir/generated-sources/myplugin-xyz"
    }
    addConfig("bar") {
        inputDirectory = "$projectDir/src/main/abc"
        outputDirectory = "$buildDir/generated-sources/myplugin-abc"
    }
}

That is a function in the task, not an extension. But could work too of course if properly done.

ok, i'll try that. thanks for your help! you don't have, by chance, example code for this at hand?

As I made various suggestions, hard to tell which you refer to. 🙂 But probably nothing at hand right now anyway, no. 😞

okay, i misinterpreted

That is a function in the task, not an extension.

as i said, i'll read the docs first and try to understand the components better. then i'll revisit your suggestions. if i haven't found a solution by then i'll come back here.