This message was deleted.

Given the java plugin’s lifecycle, you don’t want to have assemble depend on the code generation, as that’s way too late in the lifecycle. Compilation happens many steps before, which is what gradle is flagging here.

so, what would you suggest? Give up the dependency and call it manually?

I think you get implicit dependencies if you add the generated folder to the main sourceset though. That would allow gradle to figure out the dependencies by itself.

this should do it?

sourceSets {
    main {
        java.srcDir("$buildDir/generated")
    }
}

it might be

sourceSets.main.kotlin

. Not sure how java and kotlin relate to eachother.

compileKotlin.dependsOn(generateCode)

did do it indeed, thanks now I get the same for

sourcesJar

and I'll do the same

does your generateCode task mark the generated folder as its output? perhaps gradle doesn’t see the link 🤔 because chasing down all these dependencies is why you’d like for gradle to do it implicitly

Possibly you can declare an (implicit) dependency between the task and the source set using Gradle’s

builtBy

function. See an example in this section: https://docs.gradle.org/current/userguide/more_about_tasks.html#sec:link_output_dir_to_input_files

note also that you don’t need the

getByName

if you use kotlin dsl, this task has an accessor:

tasks.sourcesJar

It depends whether the goal is to include the sources only into the

sourcesJar

artifact, or to actually compile them and include in the binary artifact. In the latter case, I think,

sourcesJar

is the wrong path, and the generated sources must be included in the

main

source set (after which they will automatically be included in the

sourcesJar

).

note also that you don’t need the

getByName

if you use kotlin dsl, this task has an accessor:

tasks.sourcesJar

I can't see it

If you do it this way, I suppose, Gradle does not see the direct dependency between the

main

source set and the output of the task, because they are connected only via the directory name.

then what do you mean by

generated sources must be included in the

main

source set (after which they will automatically be included in the

sourcesJar

how shall I do it?

By that I mean that you still want to include the generated sources in the source set, but you need to do it in a way that introduces a dependency between the source set and the

generateSources

task.

and that's where

builtBy

comes into play?

Yes, this is my current theory

ok, so,

builtBy

looks to be available only on `Property`s, how can I use that in my case? I'd need somehow to have the input files for

kotlinCompile

call

builtBy(generateCode

sourceSets.main.kotlin.srcDir("$buildDir/generated", "builtBy" to "generateSources")

I believe this should work

I don’t think there is an overload in Kotlin the accepts the map. Is there?

no it's not

I think I found a solution.

builtBy

was in the right direction, but not available in the scope we want.

oh, sorry, you can only specify that on the output of the sourceset, so

sourceSets.main.output.dir("$buildDir/generated", "builtBy" to "generateSources")

First of all, I think you should remove the custom

kotlin

extension that you declare, to not get confused:

val SourceSet.kotlin: SourceDirectorySet

After that all you need to do is this:

kotlin {
    sourceSets["main"].kotlin.srcDir(generateSources.get().outputs.files)
}

The important difference with all the approaches above is that we have a live instance of

generateSources

task, and we take the reference to it’s output file collection. This collection tracks dependencies. Because of this the main source set now depends on the

generateSources

task, and you don’t need to duplicate the

"$buildDir/generated"

path at all (which is not advised anyways).

ok, I just tried, only

tasks {
    ..
    kotlin.sourceSets["main"].kotlin.srcDir(generateCode.get().outputs.files)
}

running

assemble

, I see

generateCode

is called properly before

compileKotlin

(and the generated directory is also properly marked by Idea as src folder) but I do still get the warning on

sourcesJar

> Task :generateCode

> Task :compileKotlin UP-TO-DATE

> Task :compileJava NO-SOURCE

> Task :pluginDescriptors UP-TO-DATE

> Task :processResources UP-TO-DATE

> Task :classes UP-TO-DATE

> Task :inspectClassesForKotlinIC UP-TO-DATE

> Task :jar UP-TO-DATE

> Task :javadoc NO-SOURCE

> Task :javadocJar UP-TO-DATE

> Task :sourcesJar

Execution optimizations have been disabled for task ':sourcesJar' to ensure correctness due to the following reasons:

- Gradle detected a problem with the following location: '/home/elect/IdeaProjects/gradle-catalog/build/generated'. Reason: Task ':sourcesJar' uses this output of task ':compileJava' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.4.2/userguide/validation_problems.html#implicit_dependency for more details about this problem.

Ps: I also pushed in case you want to try this yourselves

I don’t immediately see where you configure the sources jar at all. But consider adding

java {
    withSourcesJar()
}

To the build script. Seems to be working for me:

$ gw --console plain :lib:assemble 
> Task :lib:generateSources
> Task :lib:compileKotlin UP-TO-DATE
> Task :lib:compileJava NO-SOURCE
> Task :lib:processResources NO-SOURCE
> Task :lib:classes UP-TO-DATE
> Task :lib:inspectClassesForKotlinIC UP-TO-DATE
> Task :lib:jar UP-TO-DATE
> Task :lib:sourcesJar
> Task :lib:assemble

BUILD SUCCESSFUL in 1s

thanks for the heads up, I just updated to it however this

java {
    withSourcesJar()
}

didn't solve yet the warning about

sourcesJar

I'm still puzzled why I get the warning about it but if the moment I try to configure it (

getByName("sourcesJar") { .. }

) then I have the following error:

Task with name 'sourcesJar' not found in root project 'gradle-catalog'.