ComponentTreeDepsProcessor generates code in a non-deterministic order, breaking caching

We’re still on v2.38.1 so it’s possible this has been fixed, but I didn’t notice anything in the release notes.

We don’t have solid repro steps, but we’ve noticed that every so often, our HiltApplication_ComponentTreeDeps.java file generates a file that has the same content, but different ordering, causing an unnecessary rebuild.

It seems to happen within the aggregatedDeps property of the @ComponentTreeDeps annotation, although I don’t know that it’s limited to that.

[bcorso]

Playing around with it a bit, I think the order is correlated to what is being built. In particular, a clean build will always reproduce the same output, but an incremental build will produce different output depending on which sources needed to be rebuilt. IIUC, when we’re grabbing elements from a package, the most recently processed sources will appear last in the list.

Thus, we can’t hope for a well defined ordering of elements from these packages, and I think our only option here is just to manually sort them ourselves.

Thanks for reporting! I’ll look into getting a fix for this soon.

[bcorso]

Ah, thanks I did miss the part about making the change. I am now able to reproduce it, thanks!