This message was deleted.

// Register a custom task of type Copy
tasks.register<Copy>("copyDirtySrcToBuild") {
    // Configure the task to copy files from src to build/copied directory
    if(layout.projectDirectory.dir("src").asFile.exists()) {
        from(layout.projectDirectory.dir("src"))
        exclude("**/*.java")
        // "build/classes/java/main"
        into(layout.buildDirectory.dir("classes/java/main"))
    }
    mustRunAfter("compileJava")
}
// Make the build task depend on the custom copy task
tasks.named("build") {
    dependsOn("copyDirtySrcToBuild")
}
tasks.named("jar") {
    dependsOn("copyDirtySrcToBuild")
}
tasks.named("compileJava") {
    dependsOn("copyDirtySrcToBuild")
}

It seems that I need to add a bunch of those dependsOn? Otherwise the task will fail.

The answer to your initial question is simple

Indeed, I had a lot of trouble setting it up. But the thing is as I am working in a very large old Eclipse based project, some sub project, I haven't checked how many and which, having some important files just saved besides their src file. And when I launch my application, which is using OSGi framework, for local dev there is a config in OSGi to point to the folder that contains classes, then the running class will look for the file besides itself... So in order to be able to use gradle also build and run my large application, I sort of need a solution that can keep those dirty files into the build/classes folder... 🤔

As I said, there is no clean way and you really shouldn't do it. There are ways to make OSGi work properly, I played with OSGi in the past, but I do not have something I could share. It might also highly depend on the project at hand. Maybe you could instead add one new

Sync

task that collects everything into a new directory and use that to run OSGi against instead of the

compileJava

output folder. Something like

val foo by tasks.registering(Sync::class) {
    from(sourceSets.main.get().output)
    into(layout.buildDirectory.dir("foo"))
}

given the sources and resources are properly configured for the

main

source set.

Aha, that do sounds like some good idea - then I will need to also figure out a way to get those files into jars, if I change the setup?

If the point "given the sources and resources are properly configured for the

main

source set." is true, they will also be added to the jars already

Hmmm... interesting, so you mean to set the "resources" onto this synced folder foo? 🤔 For now I completely just set the "resources" folder to literally "xxxxxxx" as it cannot play well with the Eclipse folder structure here...

Probably just something like this:

sourceSets {
    main {
        resources {
            srcDir("src")
        }
    }
}

Wouldn't that also get all the java file injected and dumped in jars in the end? 🤔

Should be, yes

Woo, the Sync task seems working pretty well. Thank you so much. Maybe I should try write this in stackover flow, tried search around so many and could not find correct tips.

It might be a bit strange, the dependency, but it should not be a problem. You just say to always execute that task after

compileJava

was run successfully (successfully because you also have a dependency on the

compileJava

output)

Great, thank you so much, test it a bit seems working pretty well 🙂