melix
09/16/2024, 2:28 PMConfigurableFileCollection. It's been several times that I have a similar use case. In the context of GraalVM native build tools, there's a classpath for compilation, which is built from several different things. It is therefore using ConfigurableFileCollection. The user may add whatever they want in there, a Configuration, a File, ... However, for some features, I have to reason about the kind of files that are part of this collection. In particular, I need to be able to reason about the GAV coordinates of an artifact. Obviously, a File doesn't give us this information. The closest thing that I can use is an ArtifactView, but it only works for things that I handle, e.g, if I configure the default classpath to be derived from a Configuration, I can reason about it, but who knows what the user would do: clear the collection, add files, add more `Configuration`s, etc. Is there any chance we can get an API which wouldn't be just getFiles() but something richer that we can reason about?