generatesSources() fails, but doesn't attempt to compare like to like about compile-testing HOT 7 OPEN

So, I like the idea, but there are some issues. JavaFileObject has no notion of file path. You have the full URI (and you may remember the issues with getting the path from that…) and the file contents. That's pretty much it. I don't think that any sort of 2-tier matching is in the works, but a nice list of "These files looked kind of similar" might be really helpful.

from compile-testing.

Oh... right - it's the class name, not the path that goes into it. Hmm. That sucks. I guess I don't care so much about the mechanism, as much as the outcome, and yeah, the similarity list might work well.

from compile-testing.

This just bit me hard for about 45m. Had to debug through a few times to realize the file path had no relevance and a typo in generated source was causing the failure.

You have the full URI (and you may remember the issues with getting the path from that…)

Is there an explanation here that's relatively brief?

from compile-testing.

The issue with the path is that jar URLs don't have paths in the sense that you'd hope. It would just require special-casing throughout to hand them properly.

from compile-testing.

Would package + class name suffice as something to at least do file-based matching?

At the very least, the error message here is misleading and could use a wording change.

from compile-testing.

Oh, yes. Wow. That's a pretty bad message. We should definitely change that.

from compile-testing.

Is it possible to actually test again the generated file with another test?

from compile-testing.