From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

As a workaround you could use the project dir and the paths api to get the normalized path. 

Like pass `project.rootDir` as an `@Internal` property?

```  // Path to the project directory, internal to make the cache relocatable
  @get:Internal
  var rootDir: String? = null```
?

`rootDir` is not what I want because the normalized path is computed relative the "roots" of the file collection, not `rootDir` , see also <https://gradle-community.slack.com/archives/CA745PZHN/p1705335182134659>

Oh, okay but how should it work? It’s possible to have multiple root dirs in a file collection. 

That's my problem :sweat_smile: , Gradle does it using <https://github.com/gradle/gradle/blob/fc63c5e5edb023351e25c73188fa0d9386972b0e/subprojects/core/src/main/java/org/gradle/internal/fingerprint/impl/DefaultFileCollectionSnapshotter.java#L47|internal APIs> but I don't think it's doable without this

Ideally I'd like something that iterates the files and gives me (normalizedPath + File) together

Or getting `fileCollection.roots()` would work too and I could compute the normalized path myself

What happens if you use `FileCollection.asFileTree`?

A file tree only has a single root, right?

And in all cases I can't find an API to get the root of a `FileTree` it's all about iterating files

I think getAsPath returns the root :thinking_face: 

Was just trying that :slightly_smiling_face: It returns a column separated list of files
```val files = project.files()
files.from(fileTree("dir1"), fileTree("dir2"))

println(files.asFileTree.asPath) // "dir1/a.txt:dir2/b.txt"```

I opened <https://github.com/gradle/gradle/issues/27836>