Lóránt Pintér

This feels too early. We shouldn't start nagging when the only replacement is `@Incubating`. Let's wait until at least 8.4 with this.

This is on the drawing board, but it is not prioritized as of now.

If this happens to someone, could you give us some more information: - Are there any files or directories in the directory mentioned in the error message, or is it...

@enaess I can reproduce this by deleting the contents of `/Users/xxxxxxx/workspace/xxxxxxx/.gradle/8.6/dependencies-accessors/6c0c058358bdc002075ce61dc3018a8b2862532c/` manually between builds. If I also delete the directory `6c0c058358bdc002075ce61dc3018a8b2862532c` or any of its ancestors, then I cannot reproduce...

Could you elaborate on the use case some more? It should be perfectly fine for the task not to create the `@OutputFile` (or delete it if it exists already). But...

Why would you generate that file in the `src` directory hierarchy in the first place? Gradle recommends separating your primary inputs (i.e. source files) that you keep checked into version...

Let me close this issue as @mgroth0's problem seems to have come from creating the output outside `$buildDir`. @v1nc3n4 if you would like to request configurable parent directory creation as...

While making reproducible builds the default is not something we are planning to do in the foreseeable future, tracking the Java version that makes it into the `module-info.class` sounds like...

I think we sould come back here and reevaluate our position on reproducible archives. This is not an area we are currently focusing on though, so I can't promise exactly...

@blindpirate could you please try to reproduce this?